[
https://issues.apache.org/jira/browse/IGNITE-29170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Werner updated IGNITE-29170:
-----------------------------------
Description:
Currently, the event "First %d long running cache futures [total=%d]" is only
reported via the log by GridCachePartitionExchangeManager.
There is no way to track how often such events occur without parsing (grepping)
the log.
We need to expose this as a metric so the count of events can be monitored
through the metrics subsystem (e.g. JMX, system views, exporters) instead of
relying on log parsing.
was:
Currently, the event "Query produced big result set" is only reported via the
log by HeavyQueriesTracker.
There is no way to track how often such events occur without parsing (grepping)
the log.
We need to expose this as a metric so the count of events can be monitored
through the metrics subsystem (e.g. JMX, system views, exporters) instead of
relying on log parsing.
> 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
>
> Currently, the event "First %d long running cache futures [total=%d]" is only
> reported via the log by GridCachePartitionExchangeManager.
> There is no way to track how often such events occur without parsing
> (grepping) the log.
> We need to expose this as a metric so the count of events can be monitored
> through the metrics subsystem (e.g. JMX, system views, exporters) instead of
> relying on log parsing.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
