21 Dec 2017 12:53 AM - last edited on 19 May 2023 12:33 AM by Michal_Gebacki
We have several plug-ins in dynatrace managed and Saas. Whether the metrics collected by those plugins will be used by co-relation engine to determine the root cause of a issue or we just collect those metrics and display in respective pages and create problems when certain thresholds are breached.
Ex: Web request response time is very high on Application "A" and it's due to a malfunctioning of downstream Application "B" which results stuck treads on Application "A". If we have the JMX plugin enabled we are able to get the stuck thread count value.
Will the Co-relation engine use this metrics as well to tell us the cause for high response time and stuck thread is due to malfunctioning of application B.
Note: The Stuck Thread Count value is collected by JMX Plugin using the OneAgent.
Solved! Go to Solution.
AFAIK custom metrics are not (yet) taken into account in root cause analysis. At this time you are only able to collect, visualize and and evaluate metrics using custom alerts.
Currently, if JMX plugin fires event (not alert) on this metric then metric will be included in root cause analysis. In near future our AI will be capable to detect
root-causes in metrics without events.