Distributed Traces Showing Up Under Incorrect Service(s)

[ASE]

We're having an intermittent problem where "Fail rate increase" Problem Alerts are being triggered for our services.

When we begin troubleshooting the failing service (by viewing the service in the Services app) and review the Distributed Traces, we are finding traces (Request/Endpoint) that do not belong to the failing service.

Any thoughts as to why this is happening?

Thank you.

[Peter_Youssef]

Hello @ASE 

It's recommended to check:

• If there are service detection rules configured against the monitored services., For example check the actual services and request segments structure against your findings.
• The Process group detection rules if these are set properly or not as process group detection rules are impacting the detection and naming of process groups and accordingly the associated services that are hosted in the Process group.
• The third point to validate the truncation of trace data: https://docs.dynatrace.com/docs/shortlink/distributed-traces-diagnostic-messages#truncation-of-trace...

Hoping it adds value.

BR,

Peter.

•