Potential ways of checking if Traces indeed doesn't has any Logs-correlated to it

[waikeat_chan]

Sometimes the traces would have no log when I click 'open logs of this trace' while sometimes it does.

Now of course I shouldn't expect 100% of the traces would have logs because my thought-process is "Not every trace necessarily generates a log entry, and not every log entry is necessarily generated by a trace".

So if my statement above is correct, then I am wondering how does all the fellow community members here answer the potential question from customer of "Well.....then if I find no logs for a certain trace, how do I know it is because indeed there is no log, or is it because Dynatrace feature somehow is not working as expected?".

Now of course we can always reply customer this is something that only their application team or developer could tell us (and I think we would be very right to reply so). But I am just curious is there something else we can try to do from our side, for checking?

Right now the only thing I can think of, is make sure I applied filters in the traces to make sure we are looking at only one URL/request of only one process of only one host. Then for each and every traces:

• If ALL traces has logs, or ALL traces has no logs. Then should means no problem on how Dynatrace works
• If some traces has logs while some other don't, then indeed needs to check with Dynatrace Support

Feel free to share your tips and tricks (or even comment)! Thanks.

Best Regards,

Wai Keat

[yanezza · Accepted solution]

Due ATM logic you should expect that not all logs will lead to a trace, even if the dt.trace.id field is populated.
In any case you can check the presence of these fields, if is existing the logs is associated with a traces:
dt.span.id, dt.trace.id, dt.trace_sampled (ps: if it is true, is meaning that the trace IS present in Dynatrace so was NOT discared)

[waikeat_chan]

Thanks yanezza, 

I thought with DT SaaS Grail and no DT Managed anymore, we won't see ATM anymore?

Best Regards,

Wai Keat

[yanezza · Accepted solution]

Hi Wai,
ATM is hitting both in SaaS and in Managed, both on DPS and in Classic. 
The logic is little different and in SaaS with Grail it is not a technical limitation but a commercial limitation.
You are elegible for a certain amount of trace volume based on the number of memory-gb host monitored.

https://docs.dynatrace.com/docs/ingest-from/dynatrace-oneagent/adaptive-traffic-management/adaptive-... 

[waikeat_chan]

Hey Yanezza,

One last question: So seems like there is no way to know it from UI right (like how we can know from the CMC page of DT Managed back then)?

Means we can only get it via DQL? If yes, can you share me the DQL to get this?