[
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 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.
was:
Currently, the event "Possible failure suppressed accordingly to a configured
handler" is only reported via the log by FailureProcessor. 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.
*Proposed change*
- Register a new metric group failure (register name: failure) in
FailureProcessor.
- Add a counter metric IgnoredFailuresCount that is incremented every time a
failure is suppressed (ignored) by the configured failure handler — i.e.
exactly where IGNORED_FAILURE_LOG_MSG is printed.
- Keep the existing log message unchanged.
- Document the new metric in docs/_docs/monitoring-metrics/new-metrics.adoc.
*Acceptance criteria*
- The metric is exposed and readable through the standard metrics subsystem.
- The metric increases by 1 for each suppressed failure and is not affected by
failures processed normally (not ignored).
- A unit test covers the above behavior.
> 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 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.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
