22 Jun 2023 10:48 AM - last edited on 23 Jun 2023 07:18 AM by MaciejNeumann
Dear All,
I wanted to share a use case related to self-time and duration in the distributed traces. There was a problem along with the root cause. The root cause associated with the problem seems false positive at first glance.
With further analysis, the root cause of the problem was the self-time, not the duration. In this case, we created a calculated metric for the method that took self-time (to avoid confusion and alert a little earlier).
Did someone experience such type of cases?
How about if the DAVIS can point out the self-time (even if it is other time) service method instead of the service method having maximum duration?
Regards,
Babar
16 Aug 2023 06:25 PM
great write up @Babar_Qayyum. this would make a great RFE!