new trace tab

docs/user-guide/explore/best-practices.md

@@ -1,5 +1,5 @@
 ---
-sidebar_position: 6
+sidebar_position: 8
 title: Explore Best Practices
 description: Best practices in Log management and Explore
 image: https://dytvr9ot2sszz.cloudfront.net/logz-docs/social-assets/docs-social.jpg

docs/user-guide/explore/exceptions.md

@@ -1,5 +1,5 @@
 ---
-sidebar_position: 4
+sidebar_position: 6
 title: Exceptions
 description: Find and highlight exceptions with Logz.io
 image: https://dytvr9ot2sszz.cloudfront.net/logz-docs/social-assets/docs-social.jpg

docs/user-guide/explore/save-search.md

@@ -1,5 +1,5 @@
 ---
-sidebar_position: 5
+sidebar_position: 7
 title: Saved Search
 description: Save your search to easily access and share them
 image: https://dytvr9ot2sszz.cloudfront.net/logz-docs/social-assets/docs-social.jpg

docs/user-guide/explore/trace-view.md

@@ -0,0 +1,60 @@
+---
+sidebar_position: 4
+title: Traces in Explore
+description: View and investigate distributed traces directly in Explore
+image: https://dytvr9ot2sszz.cloudfront.net/logz-docs/social-assets/docs-social.jpg
+keywords: [logz.io, trace, traces, explore, traces in explore, log analysis, observability]
+---
+
+
+Trace View lets you to view and analyze distributed traces directly in Explore, offering a comprehensive understanding of your system's activity. It helps correlate logs with traces to identify bottlenecks, pinpoint errors, and understand your application's complete execution path. 
+
+## Configure Trace view
+
+To enable Trace View in Explore, you’ll need:
+
+* An active Logz.io Tracing account.
+* A `traceID` or `trace_id` value for all traces. Most OpenTelemetry compliant tracing libraries automatically include traceID or trace_id. Use Logz.io’s collector to send your traces.
+* A `trace_id` value for all **logs correlated with traces**. Most OpenTelemetry compliant logging libraries automatically include trace context feature to populate it. Use Logz.io’s SDKs to send your trace context propagated logs.
+
+
+:::note
+Logs and traces are correlated using the `traceID`or `trace_id` fields. Make sure these fields have the same value in both logs and traces for proper integration with trace context.
+:::
+
+After configuring your logs and traces, expand a log entry in Explore to verify that the Trace tab displays the associated trace data.
+
+Supported integrations for Trace context:
+
+* [.NET](https://docs.logz.io/docs/shipping/Code/dotnet/#add-trace-context-1)
+* [Python](https://docs.logz.io/docs/shipping/Code/Python/#trace-context)
+
+Additional integrations will be available in future updates.
+
+
+## Viewing Traces in Explore
+
+Navigate to [Explore](https://app.logz.io/#/dashboard/explore) and select accounts that include tracing data.
+
+<img src="https://dytvr9ot2sszz.cloudfront.net/logz-docs/explore-dashboard/tracing-account-dec9.png" alt="tracing-accounts" width="500"/>
+
+Expand a log entry. The Trace tab will appear alongside the Log tab. If the log is correlated with a trace, the Trace tab displays trace data, including spans, service names, and durations. Click on a span within the trace to view the corresponding log data directly within the same interface.
+
+![open trace view](https://dytvr9ot2sszz.cloudfront.net/logz-docs/explore-dashboard/trace-view-dec9.png)
+
+
+
+## Best Practices and troubleshooting
+
+Follow these tips to ensure Trace View works seamlessly and resolve any issues with missing traces:
+
+* **Maintain Consistent Trace IDs**: Ensure the `trace_id` is consistently propagated across all services to enable proper correlation between logs and traces.
+* **Optimize Sampling and Filters**: Adjust sampling limits, refine filters, or increase the sample size to capture sufficient trace data.
+* **Verify Instrumentation**: Ensure instrumentation is set up correctly in your application and tracing libraries.
+* **Include Trace Context**: Confirm that the `traceID` or `trace_id` field is present and consistent in both logs and traces.
+* **Reconnect and Resend Data**: If traces are not appearing, try reconnecting and resending your trace data to Logz.io.
+* **Minimize Noise**: Avoid logging excessive trace data to keep logs clean and focused.
+* **Validate Regularly**: Periodically check that logs and traces are correctly linked in the Trace View tab to ensure everything is functioning as expected.
+
+
+For further assistance, contact our [support team](mailto:[email protected]).