[
https://issues.apache.org/jira/browse/IGNITE-12920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Akkuratov updated IGNITE-12920:
------------------------------------
Attachment: (was: image-2020-04-20-17-05-16-972.png)
> Static hierarchy in jmx tree
> ----------------------------
>
> Key: IGNITE-12920
> URL: https://issues.apache.org/jira/browse/IGNITE-12920
> Project: Ignite
> Issue Type: Improvement
> Reporter: Igor Akkuratov
> Assignee: Igor Akkuratov
> Priority: Major
> Attachments: image-2020-04-20-17-05-36-451.png
>
>
> Current jmx tree hierarchy depends on jvm and ignite options and contains
> classloader by default.
> !image-2020-04-20-17-05-36-451.png!
> Monitoring systems like zabbix use bean path to discover metrics. Classloader
> is been changing after node restart and monitoring systems rediscover new
> metrics. If you'll try to disable classloader with option
> {code:java}
> IGNITE_MBEAN_APPEND_CLASS_LOADER_ID=false{code}
> the jmx tree will exclude one level. This behavior excludes an opportunity to
> create single monitoring template for different deployments. It can also make
> troubles if you want to start more then one ignite instance in single jvm. In
> this case you'll have to set {color:#1d1c1d}igniteInstanceName{color}
> property to add one more level with the name of this instance. It will affect
> jmx tree hierarchy as well.
> I propose to make hierarchy unchangeable and select one of the following
> values.
> If exist instancename
> else if exist consistantId
>
> In cases with enabled persistent storage consistent id would be the same
> between node restarts, in in-memory cases you will be able to specify
> instanceName.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
