-
Notifications
You must be signed in to change notification settings - Fork 6
troubleshooting traces #882
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
✅ Deploy Preview for deluxe-empanada-3ebf3b ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
|
||
| * Check that the collector pods are running and healthy. | ||
|
|
||
| * Ensure your instrumented applications are correctly configured to send traces to the OTLP endpoint exposed by the chart (e.g., `otel-collector.monitoring.svc.cluster.local:4317`). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- in
logzio-monitoringversions +7.x.x, they need to uselogzio-apm-collector.monitoring.svc.cluster.local:<port> - the port can be either 4317 or 4318, depending if the output protocol of the traces that their instrumentation generates is otlp/grpc or otlp/http
|
|
||
| ```shell | ||
| ENV OTEL_TRACES_SAMPLER=always_on | ||
| ENV OTEL_EXPORTER_OTLP_ENDPOINT="http://localhost:4317" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the port may be 4318 too depending on the instrumentation
| value: "debug" | ||
| ``` | ||
| ### Enable debug mode for all instrumented pods |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is relevant specifically only if they are using our logzio-monitoring helm chart and they enabled the opentelemetry operetor
| If the UI doesn’t show services or operations in the dropdown menus: | ||
|
|
||
| * Restart the collector to re-send metadata (especially in OTEL setups). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks like there's a header below in the page "Distributed Tracing is not showing data in Service/Operations dropdown lists" that is also referring to the same issue, is the intention for this to act as an overview section?
8naama
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great work! 🏆
Left a few comments about the tracing troubleshooting guide, some sections seems a bit repetitive - maybe we can have the Post install troubleshooting section be a summarized common causes overview, and the headers with specific issues below would be the detailed troubleshooting steps per issue?
Also, not related to the PR, but I noticed we say in some places of the guide refer to "can't see any logs... Once your logs appear", perhaps worth to update it to traces on the way:
documentation/docs/user-guide/distributed-tracing/troubleshooting/tracing-troubleshooting.md
Lines 205 to 209 in 2976c61
| Head back to **[Open Search Dashboards](https://app.logz.io/#/dashboard/osd)** and check whether you can now see logs in the Tracing account you're trying to troubleshoot. | |
| If you still can't see any logs, contact [Logz.io's Support team](mailto:help@logz.io) for additional help. | |
| Once your logs appear in Open Search Dashboards, navigate to **Distributed Tracing > [Search](https://app.logz.io/#/dashboard/jaeger/)**. |
https://deploy-preview-882--deluxe-empanada-3ebf3b.netlify.app/docs/distributed-tracing/troubleshooting/tracing-troubleshooting/