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