Use diagnostic logging for a short, controlled interval to confirm initialization, sampling, export, retry, and shutdown behavior.
Collect diagnostics safely
- Record the current log level and configuration.
- Enable the library or collector’s supported debug logging only for the affected component.
- Reproduce one or a few uniquely identifiable requests.
- Capture timestamps, component version, sampling decisions, queue or retry messages, and sanitized errors.
- Return to the previous log level immediately after collection.
Review logs before sharing them. Remove API keys, tokens, authorization headers, personal data, payload bodies, and internal host details that are not needed for diagnosis. Debug logs can increase volume and expose attribute values; do not leave them enabled as a permanent fix.
When contacting support, include the UTC reproduction window, service and operation, deployment type, relevant versions, and the smallest sanitized excerpt that demonstrates the failure.