You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/04/17 05:50:00 UTC

[jira] [Commented] (IGNITE-6869) Implement new JMX metric for jobs monitoring

    [ https://issues.apache.org/jira/browse/IGNITE-6869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16440415#comment-16440415 ] 

ASF GitHub Bot commented on IGNITE-6869:
----------------------------------------

Github user alex-plekhanov closed the pull request at:

    https://github.com/apache/ignite/pull/3053


> 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
>            Reporter: Aleksey Plekhanov
>            Assignee: Aleksey Plekhanov
>            Priority: Major
>              Labels: iep-6, jmx
>             Fix For: 2.4
>
>
> 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
(v7.6.3#76005)