Docs » Get started with the Splunk Distribution of the OpenTelemetry Collector » Get started with the Collector for Kubernetes » Troubleshoot the Collector for Kubernetes » General troubleshooting for the Collector for Kubernetes

General troubleshooting for the Collector for Kubernetes 🔗

Debug logging for the Splunk Opentelemetry Collector in Kubernetes 🔗

You can change the logging level of the Collector from info to debug to help you troubleshoot.

To do this, apply this configuration:

service:
  telemetry:
    logs:
      level: "debug"

Export your logs 🔗

The Collector’s logs are not exported by default. If you already export your logs to Splunk Platform or Splunk Observability, then you might want to export the collector’s logs too.

For example, you can configure the Collector to output debug logs and export them to Splunk Platform or Splunk Observability:

agent:
  config:
    service:
      telemetry:
        logs:
          # Enable debug logging from the collector.
          level: debug
# Optional for exporting logs.
logsCollection:
  containers:
    # Enable the logs from the collector/agent to be collected at the container level.
    excludeAgentLogs: false

To view logs, use:

kubectl logs {splunk-otel-collector-agent-pod}

This page was last updated on Aug 05, 2024.