[
https://issues.apache.org/jira/browse/IGNITE-29055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Werner updated IGNITE-29055:
-----------------------------------
Description:
Currently, the event "Blocked system-critical thread has been detected" is only
reported via the log by WorkersRegistry.
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 "Socket write has timed out" is only reported via the log
by TcpDiscoverySpi.
There is no way to track how often such timeouts occur without parsing
(grepping) the log.
We need to expose this as a metric so the count of socket timeouts can be
monitored through the metrics subsystem (e.g. JMX, system views, exporters)
instead of relying on log parsing.
> Add a metric for detected blocked system threads to WorkersRegistry
> -------------------------------------------------------------------
>
> Key: IGNITE-29055
> URL: https://issues.apache.org/jira/browse/IGNITE-29055
> Project: Ignite
> Issue Type: Task
> Reporter: Dmitry Werner
> Assignee: Dmitry Werner
> Priority: Major
>
> Currently, the event "Blocked system-critical thread has been detected" is
> only reported via the log by WorkersRegistry.
> 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)
