k8s-opentelemetry-collector-troubleshooting

Installation
SKILL.md

OpenTelemetry Collector troubleshooting

Find out why telemetry does not pass through the OpenTelemetry Collector, and propose a fix. Read first, ask before changing. Run the investigation commands freely. Run a command under an "Ask first" line only after the user approves that exact command; if your credentials do not allow it, give it to the user to run. Never run a "Proposed fix"; hand it to the user.

A collector's config defines receivers (OTLP on 4317 for gRPC and 4318 for HTTP, Prometheus, ...), processors (memory_limiter, batch, k8s_attributes, ...), exporters (otlp_grpc, otlp_http, debug, ...) and extensions (health_check, ...), and then the service.pipelines that connect them. A component that no pipeline uses is not started at all, without a warning. The collector checks the config at start and exits with Error: ... when it is invalid. At run time it logs failed exports with the exporter's name and the error. Collectors often run as an agent (DaemonSet, sidecar) that forwards to a gateway (Deployment), so follow the data hop by hop.

Installs
20
GitHub Stars
38
First Seen
Oct 26, 2026