question

Paul H. avatar image
Paul H. asked ·

Using wildcards/variables in Incidents

I have a situation where I need to measure a java mbean. This is for a circuit breaker status check. We have about 1000 numbered circuit breakers that need to be monitored. In addition to the measure, there needs to be an associated incident that indentifies the circuit breaker that has crossed a threshold.

I know within the custom jmx measure details, I can use wildcards/asterisks to measure all of them while only creating a single measure. If this is going to be used with an incident, however, the only way I know of to identify the specific object/circuit ID is to put that information in the title of the incident(the host its coming from does not help). That would mean I would have to create 1000 separate measures and 1000 separate incidents in order for all the relevant information to be seen when an incident is triggered.

Is there a way to do this by creating a single measure with key property wildcards(*), and then a single incident where jmx key properties are passed to the incident to be displayed when triggered? Perhaps a variable in the incident name $keyproperty{name} or something along those lines?

production
10 |2000000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

1 Answer

Andreas G. avatar image
Andreas G. answered ·

Hi Paul

Have you looked at JVM Monitoring Plugin. It allows you to monitor JMX Beans. The cool thing about this plugin is that it creates dynamic measures which then allows you to define a single incident where the alert message for the incident will include the actual ObjectID to indicate that one of your "dynamic measures" exceeded a certain threshold

Please give this a try

Share
10 |2000000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.