Logs is correlated to traces despite dt.span_id, dt.trace_id, dt.trace_sampled are absent

waikeat_chan — Fri, 23 May 2025 03:49:00 GMT

I have open a ticket to Dynatrace about why traces don’t have log.

Then based on the documentation provided, the understanding is that these fields/header needs to be present for the trace-log correlation to works.

But then what I see in customer environment isn’t that.

As you can see below:

I can see the trace highlighted has logs for it when I open with 'open logs of this trace'

Since this correlation works, so by right there should be values in either of these 3 fields: dt.trace.id, dt.span.id, dt.trace_sampled.

But then when I add these 3 fields to the query, they are all null!!

So right now I really don’t know how all this works actually. (And if the 3 fields aren’t necessary for the correlation to work then I’ll be very curious on what basis the Dynatrace Support revert to us that the correlation doesn’t work because there 3 fields are null)

Best Regards,

Wai Keat

Re: Logs is correlated to traces despite dt.span_id, dt.trace_id, dt.trace_sampled are absent

marco_irmer — Fri, 23 May 2025 21:30:48 GMT

I believe the field name is actually 'trace_id' rather than 'dt.trace_id'. From what I can tell, the reference in the documentation to the fields with the dt. prefix may be out of date from before Grail was GA. The current semantic dictionary entry for logs confirms that the field name is now 'trace_id'.

topic Logs is correlated to traces despite dt.span_id, dt.trace_id, dt.trace_sampled are absent in Log Analytics

Logs is correlated to traces despite dt.span_id, dt.trace_id, dt.trace_sampled are absent

Re: Logs is correlated to traces despite dt.span_id, dt.trace_id, dt.trace_sampled are absent