17 Nov 2017 09:52 AM - last edited on 01 Sep 2022 03:02 AM by MaciejNeumann
I noticed that in Dynatrace SaaS/Managed, some problems do not bring a root cause of the problem, and others do. Is there any explanation for this behavior?
Solved! Go to Solution.
This can happen when there are gaps in instrumentation of the agent. For instance, if there is a host or process downstream that is slowing things down, but there is not a OneAgent on that host, Dynatrace would not be able to correlate the root cause back to the specific issue. Do you have any specific examples you can provide? Or know of any gaps in implementation?
If there is no root cause generated for the problem does this also mean that the visual resolution path is not generated as well? I am seeing that for problems with no root cause, there also seems to be no visual resolution path.
Further, understand that the AI is not always going to be able to identify a root cause for any number of reasons and instead of showing a guess as to a root cause it doesn't display one and instead directs you to the relevant areas so you can investigate further.
Honestly one of the great things about DT is that it can cut debugging in half, if not more. That alone makes it a great tool. When we do get an actual root cause, that's just an added bonus!