Zabbix Documentation 5.0 (current)| In development:5.0 (devel)| Unsupported:

User Tools

Site Tools



This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
manual:config:items:itemtypes:jmx_monitoring [2018/07/20 09:19]
martins-v it is possible to work with MBean classes returning non-primitive data types
manual:config:items:itemtypes:jmx_monitoring [2020/03/16 11:35] (current)
martins-v minor grammar fix
Line 105: Line 105:
   jmx[com.example:​Type=Hello,​]   jmx[com.example:​Type=Hello,​]
 +== Attributes returning tabular data ==
 +Tabular data attributes consist of one or multiple composite attributes. If such an attribute is specified in the attribute name parameter then this item value will return the complete structure of the attribute in JSON format. The individual element values inside the tabular data attribute can be retrieved using preprocessing.
 +Tabular data attribute example:
 +   ​jmx[com.example:​type=Hello,​foodinfo]
 +Item value:
 +<code javascript>​
 +  {
 +    "​a":​ "​apple",​
 +    "​b":​ "​banana",​
 +    "​c":​ "​cherry"​
 +  },
 +  {
 +    "​a":​ "​potato",​
 +    "​b":​ "​lettuce",​
 +    "​c":​ "​onion"​
 +  }
 == Problem with dots == == Problem with dots ==
Line 133: Line 155:
 == Non-primitive data types == == Non-primitive data types ==
-Since Zabbix 4.0.0 it is possible to work with MBean classes ​returning non-primitive data types, which are overriden with the **toString()** method.+Since Zabbix 4.0.0 it is possible to work with custom MBeans ​returning non-primitive data types, which override ​the **toString()** method.
 === Custom endpoint example with JBoss EAP 6.4 === === Custom endpoint example with JBoss EAP 6.4 ===