[jira] [Created] (IGNITE-12920) Static hierarchy in jmx tree

["Igor Akkuratov (Jira)" <ji...@apache.org>]

Igor Akkuratov created IGNITE-12920:
---------------------------------------

             Summary: 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
         Attachments: image-2020-04-20-17-05-16-972.png, image-2020-04-20-17-05-36-451.png

Current jmx tree hierarchy depends on jvm and ignite options and by default contains classloader.

!image-2020-04-20-17-05-36-451.png!

Monitoring systems like zabbix use bean path to discover metrics. In this case classloader would be new after each node restart. If you'll disable classloader with option {color:#1d1c1d}{color}
{code:java}
IGNITE_MBEAN_APPEND_CLASS_LOADER_ID=false{code}
{color:#1d1c1d}{color} the jmx tree would exclude one level. This behavior excludes an opportunity to create single monitoring template for different deployments. And make troubles if you want to start more then one ignite instance in single jvm. In this case you should set {color:#1d1c1d}igniteInstanceName{color} property to add one more level with instance name. And it's also changes jmx tree hierarchy.

 

I offer to make hierarchy unchangeable and select one of the following values.

If exist instancename

else if exist consistantId

 

In persistent cases consistent id  would be the same between node restarts.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)