For quick fix you can change this file*: JMXItemChecker.java*

274 // This is changed for replace special characters
275 //String key = property.getKey().toUpperCase();
276 String key = property.getKey().toUpperCase().replace('-', '_’);

I make fixed package and template: https://share.zabbix.com/official-templates/wildfly-eap-jboss-discovery

With ZBXNEXT-4877 there is no need to generate LLD macro names for {#JMX<key property>} any more. This issue can be revisited.

Problem example with default GW, normaly zabbix try create macros with original name:  data-source TO  "{#JMXDATA-SOURCE}" but "-" is not allowed in macros. (Wildfly example)

Now working default version:

root@hosting1:~# ./jmx_fix_test
[
 {

  "{#JMXDOMAIN}": "jboss.as",
  "{#JMXSUBSYSTEM}": "datasources",
  "{#JMXSTATISTICS}": "jdbc",
  "{#JMXOBJ}": "jboss.as:subsystem=datasources,data-source=ExampleDS,statistics=jdbc"
 }
]

Fixed version with using replace method:

[
 {
  "{#JMXDOMAIN}": "jboss.as",
  "{#JMXDATA_SOURCE}": "ExampleDS",
  "{#JMXSUBSYSTEM}": "datasources",
  "{#JMXSTATISTICS}": "jdbc",
  "{#JMXOBJ}": "jboss.as:subsystem=datasources,data-source=ExampleDS,statistics=jdbc"
 }
]

This key i use in discovery:
jmx.discovery[beans,"jboss.as:subsystem=datasources,data-source=*,statistics=jdbc"]

Tom

Dear Community,

This is proposed solution to the ticket.

Would like to hear your feedback.

Summary
A new JMX item key will be introduced.
Key name: jmx.get[<discovery mode>,<object name>]
Parameters:

• discovery mode - one of the following: attributes:
  • attributes - retrieve JMX MBean attributes
  • beans - retrieve JMX MBeans
• object name - object name pattern identifying the MBean names to be retrieved (empty by default, retrieving all registered beans).

The jmx.get[] *is similar to *jmx.discovery, but it does not turn Java object properties into macro names.

Example:
Request: jmx.get[beans,"com.example:type=*,*"]
Response:

[
	{
		"object": "com.example:type=Atomic",
		"domain": "com.example",
		"properties": {
			"type": "Atomic"
		}
	},
	{
		"object": "com.zabbix:type=yes,domain=zabbix.com,data-source=/dev/rand,ключ=значение,obj=true",
		"domain": "com.zabbix",
		"properties": {
			"type": "Hello",
			"domain": "com.example",
			"data-source": "/dev/rand",
			"ключ": "значение",
			"obj": true
		}
	}
]

<offtopic>I can add "(Zabbix Team)" to my name as well. What's the point?</offtopic>

Now back to JMX.

Response:

{
  "data":[
    {
      "domain":"com.example",
      "type":"Atomic"
    },
    {
      "domain":"com.example",
      "type":"Hello",
      "data-source":"/dev/rand",
      "ключ":"значение"
    }
  ]
}

There is no point of wrapping data in an object with a single key, you can return an array straight away:

[
  {
    "domain":"com.example",
    "type":"Atomic"
  },
  {
    "domain":"com.example",
    "type":"Hello",
    "data-source":"/dev/rand",
    "ключ":"значение"
  }
]

On the other hand there seems to be a good reason no introduce a more complex structure inside each object in the array. Current documentation says that {#JMXDOMAIN} and {#JMXOBJ} are "Zabbix reserved names" making it impossible to discover MBean properties named "domain" and "obj". New format allows you to separate reserved Zabbx keys and MBean properties into different "namespaces", e.g.:

[
  {
    "domain":"<Zabbix stuff>",
    "obj":"<more Zabbix stuff>",
    "properties":{
      "domain":"<MBean stuff>",
      "obj":"<also MBean stuff>",
      ...
    }
  },
  ...
]

Also old name jmx.discovery is 100% to the point, would be a mistake to deprecate it in favor of jmx.get which (no offence) says nothing.

In documentation: https://www.zabbix.com/documentation/4.4/manual/discovery/low_level_discovery/jmx

MBean properties (like

,

). Some important notes to pay attention to when defining MBean attribute name that is created from MBean property name by the following algorithm:

• attribute name case is changed to uppercase;
• attribute name case is ignored (no LLD macro is generated) in case it consists of not supported characters. Supported characters can be described by the following regular expression: “A-Z0-9_\.”;
• if an attribute name is called “obj” or “domain” it will be replaced with the values of Zabbix properties {#JMXOBJ}

  and

  {#JMXDOMAIN}

  (supported since Zabbix 3.4.3.).

alarionovs copied the wrong example of responce. I edited his comment to reflect the decisions made.

cyclone, thanks for your feedback!

Available in 4.4.0beta1 351df0216f2.

Updated documentation:

• What's new
• Discovery of JMX objects (new item key)
• Discovery of JMX objects (examples of values returned)