0

Dynatrace is confusing the contexts of the requests. The error caused by Request A is being reported in Request B. We can see in the Error tab the stack shown in Request B is from Request A.

General Timeline General Timeline

API B - Summary API B - Summary

API B - Threads API B - Threads

API A - Summary API A - Summary

API A - Threads API A - Threads

Error tab (StackTrace ) In the Error tab the exception shown is System.TimeoutException with the correct time set to 3s and in StackTrace it shows ServiceB, ControllerB when it should be ServiceB, COntrollerB

I tried to identify a pattern in the ThreadIDs or PODs even though it was a Kubernetes cluster and each request was going to different PODs and even then there was no correlation.

Alex SSantos
  • 13
  • 1
  • 8
  • I think this is best handled via a support-case to let the experts at Dynatrace take a closer look. – centic May 31 '23 at 03:21
  • I already contacted dynatrace support for the case but they take a long time and the answer they gave does not seem to me that they have the answer for the case. – Alex SSantos Jun 17 '23 at 00:08

0 Answers0