ERROR ExecProcessor - message from "python /opt/splunk/etc/apps/SPLUNK4JMX/bin/jmx.py" Error executing JMX stanza jmx://XXXX : No such attribute: yyyy

[davideperego]

Hello,
I'm getting tons of these messages in splunkd.log.

ERROR ExecProcessor - message from "python /opt/splunk/etc/apps/SPLUNK4JMX/bin/jmx.py" Error executing JMX stanza jmx://CONFIGNAME : No such attribute: attributename

I know the best is to remove the missing attributes from the xml configuration (I have hundreds of xml running), but can I filter out the messages of this type and avoid filling the log and _internal index ?

Thanks

[Damien_Dallimor · Accepted solution]

The default config.xml that ships with the App is merely an example. I've tried to make it as generic as possible , but there may well be MBean attributes declared that are not relevant to your JVM runtime. So you will have to remove them from your config file.

[davideperego]

I understand the need to correct config.xml, actually it's not my job editing it because activity is from another team, but I would like to find a way to filter out this kind of noise... _internal index growing more than actual data is a real problem to me.
Thanks, Davide

[Damien_Dallimor]

You will have to find who's job it is to edit it.
It is their responsibility to set up the config.xml file correctly.
That is the root cause of the problem you need to address.
Then , you won't see these genuine error messages.