You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Kirill Gusakov (Jira)" <ji...@apache.org> on 2022/10/21 14:20:00 UTC

[jira] [Updated] (IGNITE-17357) JMX metric exporter for Ignite 3

     [ https://issues.apache.org/jira/browse/IGNITE-17357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kirill Gusakov updated IGNITE-17357:
------------------------------------
    Description: 
Metrics should be able to be exported via JMX as a first stage of metrics exposing.

Exporter implementation must provide the following behavior:
 * for each MetricSource we need to provide separate MBean with attribute per metric
 * each MBean attribute must have the same name as corresponding metric
 * on enable/disable event for MetricSource corresponding MBean must be registered/unregistered

  was:Metrics should be able to be exported via JMX. MBeans should be dynamically created and destroyed for metric sets that are enabled for metric sources (one MBean per metric source).


> JMX metric exporter for Ignite 3
> --------------------------------
>
>                 Key: IGNITE-17357
>                 URL: https://issues.apache.org/jira/browse/IGNITE-17357
>             Project: Ignite
>          Issue Type: New Feature
>            Reporter: Denis Chudov
>            Assignee: Kirill Gusakov
>            Priority: Major
>              Labels: ignite-3
>
> Metrics should be able to be exported via JMX as a first stage of metrics exposing.
> Exporter implementation must provide the following behavior:
>  * for each MetricSource we need to provide separate MBean with attribute per metric
>  * each MBean attribute must have the same name as corresponding metric
>  * on enable/disable event for MetricSource corresponding MBean must be registered/unregistered



--
This message was sent by Atlassian Jira
(v8.20.10#820010)