Skip to content

Conversation

@Simplychee
Copy link
Contributor

@Simplychee Simplychee commented Jul 23, 2025

@netlify
Copy link

netlify bot commented Jul 23, 2025

Deploy Preview for deluxe-empanada-3ebf3b ready!

Name Link
🔨 Latest commit 2976c61
🔍 Latest deploy log https://app.netlify.com/projects/deluxe-empanada-3ebf3b/deploys/6891bf3e235adf0008e5422c
😎 Deploy Preview https://deploy-preview-882--deluxe-empanada-3ebf3b.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@Simplychee Simplychee requested a review from ralongit July 23, 2025 14:32
@Simplychee Simplychee requested a review from 8naama October 8, 2025 13:32

* 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`).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  1. in logzio-monitoring versions +7.x.x, they need to use logzio-apm-collector.monitoring.svc.cluster.local:<port>
  2. 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"
Copy link
Contributor

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
Copy link
Contributor

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

Comment on lines +29 to +31
If the UI doesn’t show services or operations in the dropdown menus:

* Restart the collector to re-send metadata (especially in OTEL setups).
Copy link
Contributor

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?

Copy link
Contributor

@8naama 8naama left a 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:

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/)**.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants