Hello,
We identified that log and trace correlation is not working in the classic view. This conclusion came after an analysis with Dynatrace Support. The application team structured the log including the TraceID and SpanID, and we configured the log processing rules. The correlation does work when we open a log and navigate to the trace, but the reverse path does not work.
An important detail is that in the new Traces application, this action works as expected.
Below is the information provided by the Dynatrace engineer:
“After further investigation into this issue, we found similar causes for this behavior, and we have classified it as a product bug. Our product team confirmed that the behavior is caused by architectural changes introduced with OpenPipeline and Service Detection V2. These updates enrich incoming logs with a service ID; however, in cases where the corresponding spans are not detected or ingested by the OneAgent, the classic trace view cannot correlate these logs as expected.
Since these changes are part of the new architecture, they cannot be easily reverted. At this time, the recommended approach is to use the new Distributed Tracing application, which is designed to correlate logs with their respective traces more reliably.”
Ticket ID:587719
Subject:Issue | Log and Trace Correlation in Classic View
