[
https://issues.apache.org/jira/browse/IGNITE-6869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16255568#comment-16255568
]
ASF GitHub Bot commented on IGNITE-6869:
----------------------------------------
GitHub user alex-plekhanov opened a pull request:
https://github.com/apache/ignite/pull/3053
IGNITE-6869 Added new JMX metric: Total jobs execution time.
Added new JMX metric: Total jobs execution time.
Added MBean to monitor aggregated cluster metrics.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/alex-plekhanov/ignite ignite-6869
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/3053.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #3053
----
commit 46384430e99135ba3aeba5a64d43c0c8c097ad8b
Author: Aleksey Plekhanov <[email protected]>
Date: 2017-11-16T16:31:16Z
IGNITE-6869 Added new JMX metric: Total jobs execution time. Added MBean to
monitor aggregated cluster metrics.
----
> Implement new JMX metric for jobs monitoring
> --------------------------------------------
>
> Key: IGNITE-6869
> URL: https://issues.apache.org/jira/browse/IGNITE-6869
> Project: Ignite
> Issue Type: New Feature
> Security Level: Public(Viewable by anyone)
> Reporter: Aleksey Plekhanov
> Assignee: Aleksey Plekhanov
> Labels: iep-6, jmx
>
> There are now some metrics in ClusterLocalNodeMetricsMXBean for monitoring
> job's execution statistics (min/max/avg execution time). But these metrics
> gathered since node started and can't be used to calculate average execution
> time between probes.
> To resolve this problem new metric "Total jobs execution time" should be
> implemented.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
