From 01e1a7eecaec88b1322177dca57533d675f6e6cf Mon Sep 17 00:00:00 2001 From: Aleksandra Spilkowska Date: Mon, 29 Sep 2025 15:01:55 +0200 Subject: [PATCH 1/2] Add cross-links between debug logging pages fro the Collector and SDKs --- .../opentelemetry/edot-collector/enable-debug-logging.md | 3 +++ .../ingest/opentelemetry/edot-sdks/enable-debug-logging.md | 3 ++- 2 files changed, 5 insertions(+), 1 deletion(-) diff --git a/troubleshoot/ingest/opentelemetry/edot-collector/enable-debug-logging.md b/troubleshoot/ingest/opentelemetry/edot-collector/enable-debug-logging.md index c421b690b7..fa94469390 100644 --- a/troubleshoot/ingest/opentelemetry/edot-collector/enable-debug-logging.md +++ b/troubleshoot/ingest/opentelemetry/edot-collector/enable-debug-logging.md @@ -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). diff --git a/troubleshoot/ingest/opentelemetry/edot-sdks/enable-debug-logging.md b/troubleshoot/ingest/opentelemetry/edot-sdks/enable-debug-logging.md index f1702e2f9a..5cd7348b1d 100644 --- a/troubleshoot/ingest/opentelemetry/edot-sdks/enable-debug-logging.md +++ b/troubleshoot/ingest/opentelemetry/edot-sdks/enable-debug-logging.md @@ -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 -c ` (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. From e9f05fc46d385314426bfa9576302b906da208ac Mon Sep 17 00:00:00 2001 From: Aleksandra Spilkowska Date: Mon, 29 Sep 2025 15:07:15 +0200 Subject: [PATCH 2/2] Apply comment --- .../ingest/opentelemetry/edot-sdks/enable-debug-logging.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/troubleshoot/ingest/opentelemetry/edot-sdks/enable-debug-logging.md b/troubleshoot/ingest/opentelemetry/edot-sdks/enable-debug-logging.md index 5cd7348b1d..fa7f7ac1fc 100644 --- a/troubleshoot/ingest/opentelemetry/edot-sdks/enable-debug-logging.md +++ b/troubleshoot/ingest/opentelemetry/edot-sdks/enable-debug-logging.md @@ -27,7 +27,7 @@ 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, and so on): * For containerized environments such as Kubernetes/Docker: * `kubectl logs -c ` (correct container name matters if there are sidecars)