https://community.dynatrace.com/t5/Log-Analytics/Navigation-between-logs-and-session-replay/m-p/249934#M129 <P>Log to trace and user session to request are two different links. Log to trace is&nbsp; based on <A href="https://docs.dynatrace.com/docs/shortlink/lma-log-enrichment" target="_self">trace context information,</A><BR />user session to trace is based on x-dynatrace headers (mobile/custom apps) or cookies/x-dtc headers (web applications).&nbsp;<BR /><BR />If you have see the dt.trace_id in your log, you should be able to open the trace (if it's captured).&nbsp;</P> Thu, 04 Jul 2024 19:51:47 GMT Julius_Loman 2024-07-04T19:51:47Z https://community.dynatrace.com/t5/Log-Analytics/Navigation-between-logs-and-session-replay/m-p/249932#M128 <P>We are working on POC for Log monitoring in SaaS. I am facing issues with log traces and span ids. I am unable to navigate between logs and session replay.&nbsp;</P> Fri, 05 Jul 2024 08:33:39 GMT https://community.dynatrace.com/t5/Log-Analytics/Navigation-between-logs-and-session-replay/m-p/249932#M128 Lakhanimayuri 2024-07-05T08:33:39Z https://community.dynatrace.com/t5/Log-Analytics/Navigation-between-logs-and-session-replay/m-p/249934#M129 <P>Log to trace and user session to request are two different links. Log to trace is&nbsp; based on <A href="https://docs.dynatrace.com/docs/shortlink/lma-log-enrichment" target="_self">trace context information,</A><BR />user session to trace is based on x-dynatrace headers (mobile/custom apps) or cookies/x-dtc headers (web applications).&nbsp;<BR /><BR />If you have see the dt.trace_id in your log, you should be able to open the trace (if it's captured).&nbsp;</P> Thu, 04 Jul 2024 19:51:47 GMT https://community.dynatrace.com/t5/Log-Analytics/Navigation-between-logs-and-session-replay/m-p/249934#M129 Julius_Loman 2024-07-04T19:51:47Z