Use OpenTelemetry diagnostic exporters without exposing real payloads

Detailed Collector debug output can print the entire telemetry payload.

Source facts

The Collector troubleshooting guide uses the debug exporter to confirm receiving, processing and exporting data. With verbosity set to detailed, the debug exporter prints the entire payload. The guide also describes zPages for live receiver and exporter diagnosis, including errors the Collector may not otherwise emit.

Source: OpenTelemetry documentation — Troubleshooting.

Applicability

Review Collector debug-exporter output and zPages live troubleshooting before choosing diagnostic exposure.

DSE recommendation

DSE recommends reproducing the issue with synthetic signals before enabling verbose output on real workloads. Decide whether the failing stage is receipt, processing, or export and add only the diagnostic visibility needed for that question. Restrict endpoint access and log retention, remove credentials from configuration excerpts, and establish a cleanup time for temporary exporters. Keep payload inspection under the same data-handling rules as the original application observations. A debugging change should have an owner and a clear end condition.

Verification

In an isolated pipeline, send a harmless identifiable signal and observe the intended diagnostic stage. Confirm detailed output and endpoint access stay within the approved audience. Remove temporary diagnostics afterward and verify the ordinary pipeline still delivers to its intended destination without retaining unnecessary payload copies. Retain the diagnostic configuration and its removal checkpoint with the synthetic result. Have the data owner approve any remaining output destination or endpoint before repeating the investigation with operational telemetry.

Official reference

OpenTelemetry documentation — Troubleshooting. Reviewed October 20, 2026.