[
https://issues.apache.org/jira/browse/IGNITE-29170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18132221#comment-18132221
]
Ignite TC Bot commented on IGNITE-29170:
----------------------------------------
Monitoring: Added metrics for the count and maximum duration of long-running
cache futures.
The Release Note field has been filled with the wording above. Please review it
and edit it if needed.
> Add a metric for long running cache futures
> -------------------------------------------
>
> Key: IGNITE-29170
> URL: https://issues.apache.org/jira/browse/IGNITE-29170
> Project: Ignite
> Issue Type: Task
> Reporter: Dmitry Werner
> Assignee: Dmitry Werner
> Priority: Major
> Labels: metrics-to-log
> Fix For: 2.19
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Currently, long running cache futures are only reported via the log warning
> "First %d long running cache futures [total=%d]" from
> GridCachePartitionExchangeManager.
> There is no way to monitor them without parsing logs.
> It is proposed to add two metrics to the tx metrics registry
> (TransactionMetricsAdapter):
> - LongRunningCacheFuturesCount — the number of in-progress cache futures
> whose duration exceeds longOperationsDumpTimeout;
> - MaxCacheFutureDuration — the maximum duration of in-progress cache futures,
> in milliseconds.
> Both are computed from GridCacheMvccManager active and atomic futures, so
> they are exposed through all metric subsystems (JMX, exporters, system views)
> with no log parsing required.
> The existing warning behavior is unchanged. Covered by
> GridCachePartitionExchangeManagerWarningsTest; documented in
> monitoring-metrics/new-metrics.adoc.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
