[IGNITE-12920] Static hierarchy in jmx tree - ASF JIRA

Agile Board

Attach files

Attach Screenshot

Add vote

Voters

Watch issue

Watchers

Create sub-task

Link

Clone

Update Comment Author

Replace String in Comment

Update Comment Visibility

Delete Comments

XML

Word

Printable

JSON

Details

Type: Improvement
Status: Patch Available
Priority: Major
Resolution: Unresolved
Affects Version/s: None
Fix Version/s: None
Component/s: None
Labels:
None

Ignite Flags:

Docs Required, Release Notes Required

Description

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

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

IGNITE_MBEAN_APPEND_CLASS_LOADER_ID=false

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 igniteInstanceName 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.