Thank you for your comments. We are mainly interested in the queue depth. Will this configuration work?
Our objective is to alert when a certain number increases in the Queue Depth for a certain time and for a certain group of the Queues.
I'm unable to follow. As far as I know, there is no queue depth metric, as in, 'Queue Depth'.
Sample metric is : builtin:tech.kafka.kafka.network.RequestChannel.RequestQueueSize.Value
Can you take a screenshot and show me the queuedepth metric you are referring to?
Another Sample, for you, if I go ahead with the below Configuration, the Custom_Alert will be a catch_all for "Queue Depth" across all services/queues/dimensions with by the names like "CLOUD_"
you are almost there, the specific metric you want is indeed ext:tech.IBMMQ_Java.Queue.Depth
That metric will have the different queues as dimensions, which you can select on which one to alert on a desired depth.
This is a metrics based off the queues, you can identify this in the metric key, from left to right like a drop down ext:tech.IBMMQ_Java.Queue.Depth
You can identify on which entity the metric is based (dimension) by looking at the highlighted section below
Thank you for your comments. The discussion started from the same point. We can definitely use the dimension filter but in this way, you will have to create too many rules. Our objective is to achieve through one rule.
You can add the desired queues to a specific management zone
Or tag all important queues
You can tag (or by this means also use the following rule in a management zone) e.g. using properties/tags of the underlying process groups of the queues with following selector