[
https://issues.apache.org/jira/browse/IGNITE-29054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Werner updated IGNITE-29054:
-----------------------------------
Description:
Currently, the event "Possible too long JVM pause" is only reported via the log
by LongJVMPauseDetector.
There is no way to track how often such JVM pauses occur without parsing
(grepping) the log.
We need to expose this as a metric so the count of suppressed (ignored)
failures can be monitored through the metrics subsystem (e.g. JMX, system
views, exporters) instead of relying on log parsing.
was:
Currently, the event "Possible too long JVM pause" is only reported via the log
by LongJVMPauseDetector.
There is no way to track how often such failures occur without parsing
(grepping) the log.
We need to expose this as a metric so the count of suppressed (ignored)
failures can be monitored through the metrics subsystem (e.g. JMX, system
views, exporters) instead of relying on log parsing.
> Add long JVM pause count metric to LongJVMPauseDetector
> -------------------------------------------------------
>
> Key: IGNITE-29054
> URL: https://issues.apache.org/jira/browse/IGNITE-29054
> Project: Ignite
> Issue Type: Task
> Reporter: Dmitry Werner
> Assignee: Dmitry Werner
> Priority: Major
>
> Currently, the event "Possible too long JVM pause" is only reported via the
> log by LongJVMPauseDetector.
> There is no way to track how often such JVM pauses occur without parsing
> (grepping) the log.
> We need to expose this as a metric so the count of suppressed (ignored)
> failures 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)
