21 Mar 2023 04:17 AM - last edited on 12 May 2023 12:44 AM by Michal_Gebacki
There is a custom plugin that we have downloaded from the Dynatrace support site and uploaded in the Dynatrace Under the settings section.
When we checked the plugin json, we can see the entity is mapped to PROCESS_GROUP_INSTANCE instead of QUEUE
Can you please help us to understand why the entity name for QUEUE would be specified under PROCESS_GROUP? not QUEUE?
Also is it fine to change the value and upload it as a separate plugin and see how the data flows?
Solved! Go to Solution.
Extensions in the first framework can either map to a host or a process group instance. It cannot map to a queue.
That being said, what extension are you talking about? Can you provide a link?
Hi @Mike_L ,
We are trying to fetch the "Message pending count" and "Message current count" for the jmx queues using the custom plugin-Thread_Analysis (version 1.1657608853) which has Entity type as "PROCESS_GROUP_INSTANCE" as dynatrace does not capture these data by default.
And using these metrics , we are creating SLO for the queues which has Entity type as "Queue". But we are facing error while creating due to mismatch in Entity type .
Can you please help me on how SLO's can be created for the jmx queues (if there is any other way).
In not too long we will release JMX extensions in extension framework 2.0. As part of that improvement we will allow the JMX extension creator to use the generic topology to define any topology they want instead of being limited by hosts and process group instances. That should resolve your use case.
Map the metrics to a process group instance and use the metrics there as part of the SLO. That should work, although it depends a bit on how you need to do visualizations and splittings.