Hello all,
I am trying to set up a monitor for JMX items where multiple values in the MBEAN path can potentially change. The index values and ip values are able to change, however my discovery rule is able to get those values. My main issue is the job value is a string with a long GUID appended to it whose value I cannot get. I was wondering if there was a way for me to use a wildcard in the jmx function to take care of this?
Example:
job="diego_database-partition-8e385c3fd158b55988ba" where the GUID can change
jmx["org.cloudfoundry:deployment=cf,job=*,index={#PROP INDEX},ip={#PROPIP}","opentsdb\.nozzle\.bbs\.Crash edActualLRPs"]
So far I have been unsuccessful in my attempts and am trying to avoid using an external agent to get the values and map them.
Any help would be greatly appreciated.
Thank you!
I am trying to set up a monitor for JMX items where multiple values in the MBEAN path can potentially change. The index values and ip values are able to change, however my discovery rule is able to get those values. My main issue is the job value is a string with a long GUID appended to it whose value I cannot get. I was wondering if there was a way for me to use a wildcard in the jmx function to take care of this?
Example:
job="diego_database-partition-8e385c3fd158b55988ba" where the GUID can change
jmx["org.cloudfoundry:deployment=cf,job=*,index={#PROP INDEX},ip={#PROPIP}","opentsdb\.nozzle\.bbs\.Crash edActualLRPs"]
So far I have been unsuccessful in my attempts and am trying to avoid using an external agent to get the values and map them.
Any help would be greatly appreciated.
Thank you!