Skip to content

Add cross-links between debug logging pages for the Collector and SDKs #3210

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.

Sign up for GitHub

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

Merged
merged 2 commits into from
Sep 29, 2025
Merged

Add cross-links between debug logging pages for the Collector and SDKs #3210

Show file tree
Hide file tree
Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
01e1a7e
Add cross-links between debug logging pages fro the Collector and SDKs
alexandra5000 Sep 29, 2025
e9f05fc
Apply comment
alexandra5000 Sep 29, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions troubleshoot/ingest/opentelemetry/edot-collector/enable-debug-logging.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -86,3 +86,6 @@ Debug logging for the Collector is not currently configurable through {{fleet}}.
:::


## Resources

To learn how to enable debug logging for the EDOT SDKs, refer to [Enable debug logging for EDOT SDKs](../edot-sdks/enable-debug-logging.md).
3 changes: 2 additions & 1 deletion troubleshoot/ingest/opentelemetry/edot-sdks/enable-debug-logging.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -27,7 +27,8 @@ Enabling debug logging can help surface common problems such as:

## Verify you're looking at the right logs

* Ensure you’re checking logs for the same process that starts your app (systemd service, container entrypoint, IIS worker, etc.).
Ensure you’re checking logs for the same process that starts your app (systemd service, container entrypoint, IIS worker, etc.):

* For containerized environments such as Kubernetes/Docker:
* `kubectl logs <pod> -c <container>` (correct container name matters if there are sidecars)
* Check the new Pod after a rollout, as old Pods may show stale environment without your debug flags.
Expand Down
Loading