[
https://issues.apache.org/jira/browse/IGNITE-29229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Egor Baranov updated IGNITE-29229:
----------------------------------
Labels: metrics monitoring (was: )
> Add AssertionErrorCount monitoring metric to detect AssertionError
> occurrences in the JVM
> -----------------------------------------------------------------------------------------
>
> Key: IGNITE-29229
> URL: https://issues.apache.org/jira/browse/IGNITE-29229
> Project: Ignite
> Issue Type: New Feature
> Reporter: Egor Baranov
> Assignee: Egor Baranov
> Priority: Major
> Labels: metrics, monitoring
>
> There is currently no way to detect AssertionError occurrences in the node
> JVM. These errors are frequently swallowed by catch (Throwable) blocks (500+
> in the codebase), making them
> invisible during test runs.
> This change adds a LongAdderMetric named sys.AssertionErrorCount to
> GridMetricManager. The metric is backed by a JFR jdk.JavaErrorThrow event
> consumer (RecordingStream) that listens
> for thrown java.lang.AssertionError events and increments the counter.
> The stream is started/stopped with the manager lifecycle.
> The metric is exposed through all standard export channels (SQL metrics
> system view, JMX, REST) and requires no JVM agent.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
