[
https://issues.apache.org/jira/browse/IGNITE-29107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18133745#comment-18133745
]
Ignite TC Bot commented on IGNITE-29107:
----------------------------------------
Docs Required triage: removed the Docs Required flag because merged PR #13661
already documents MaxRunningComputeTasksPerConnection, the CLIENT_CONNECTIONS
ACTIVE_COMPUTE_TASKS column, and the metric configuration command in
docs/_docs/monitoring-metrics/{new-metrics.adoc,new-metrics-system.adoc,system-views.adoc}
and docs/_docs/tools/control-script.adoc.
> Add ClientConnector metric for current peak of running compute tasks
> --------------------------------------------------------------------
>
> Key: IGNITE-29107
> URL: https://issues.apache.org/jira/browse/IGNITE-29107
> Project: Ignite
> Issue Type: Task
> Reporter: Ilya Shishkov
> Assignee: Ilya Shishkov
> Priority: Minor
> Fix For: 2.20
>
> Time Spent: 2h 50m
> Remaining Estimate: 0h
>
> Add `ActiveComputeTasksPerConnection` metric to the client.connector
> registry (available via JMX/read API) - the maximum number of active compute
> tasks across all active thin-client connections.
> Metric can implement `MaxValueMetric` to overcome peak losses caused by
> monitoring poll timings.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
