- Home
- Skills
- DevOps & Cloud
- OpenTelemetry Collector Check
More screenshots
Works with the AI Agents you already use
OpenTelemetry Collector Check
Check OpenTelemetry Collector configs, Helm values and OTEL_* settings before you deploy: vendor keys in headers, keys sent without TLS, pipelines that stop the Collector starting, open receivers and risky defaults.
$5
OpenTelemetry Collector Check
Example session with this skill installed
Check this project with opentelemetry-collector-check.
- Read your context and instructions
- Compiled the opentelemetry collector check
$ python3 scripts/check_otel.py examples/risky
BLOCK docker-compose.yml:8 O02 SECRET_IN_OTEL_ENV
OTEL_EXPORTER_OTLP_HEADERS: x-honeycomb-team=<redacted>
Why: A credential is written into OTEL_EXPORTER_OTLP_HEADERS (or a per-signal _HEADERS variable, the otel.exporter.otlp.headers property, or a -D flag in JAVA_TOOL_OPTIONS), or into a secret-named variable of a Collector container, in a Compose file, Kubernetes manifest or Secret, Helm values, Dockerfile, shell script or .properties file. These files are committed and copied into images and logs, so the key works for anyone who reads them.
Safer: Rotate the key and inject it at run time: a Kubernetes secretKeyRef (then $(NAME) inside the header value), Compose ${NAME} from an .env file git ignores, or your platform's secret store. Never bake it into an image with ENV or ARG.
BLOCK docker-compose.yml:13 O02 SECRET_IN_OTEL_ENV
BLOCK otel-collector.yaml:34 O01 SECRET_IN_COLLECTOR_CONFIG
BLOCK otel-collector.yaml:36 O03 CREDENTIALS_WITHOUT_TLS
BLOCK otel-collector.yaml:62 O04 UNDEFINED_COMPONENT
REVIEW otel-collector.yaml:7 O15 DEBUG_ENDPOINT_EXPOSED
REVIEW otel-collector.yaml:8 O14 REMOVED_COMPONENT
REVIEW otel-collector.yaml:13 O18 WEAK_OR_PLACEHOLDER_CREDENTIAL
REVIEW otel-collector.yaml:19 O11 RECEIVER_ON_ALL_INTERFACES
REVIEW otel-collector.yaml:21 O11 RECEIVER_ON_ALL_INTERFACES
REVIEW otel-collector.yaml:42 O16 TLS_OFF_OR_WEAK
REVIEW otel-collector.yaml:45 O17 ENV_VAR_NOT_EXPANDED
REVIEW otel-collector.yaml:48 O12 DEBUG_EXPORTER_DETAILED
REVIEW otel-collector.yaml:49 O14 REMOVED_COMPONENT
REVIEW otel-collector.yaml:57 O13 MEMORY_LIMITER_MISSING
REVIEW otel-collector.yaml:59 O13 MEMORY_LIMITER_MISSING
(Each finding also has Why and Safer lines, as in the first one.)
Verdict: BLOCK. Checked 2 files, 2 with OpenTelemetry content.
This is a static check of file text. NOT FLAGGED is not a guarantee.
Connects securely to your tools. The creator never sees your data.
About this skill
A vendor API key pasted into an exporter's x-honeycomb-team or Authorization header, or into OTEL_EXPORTER_OTLP_HEADERS in a Compose file, ends up in git, in the ConfigMap and in every image built from it. A pipeline that lists otlphttp/vendor when the exporter is defined as otlp_http/vendor stops the Collector from starting at all, and a header written as $API_KEY is sent as that literal text, because the Collector no longer expands bare $NAME values. This skill finds those and the other Collector mistakes below before you deploy, and tells you how to fix each one.
Your agent runs a scanner on Collector config files, values for the opentelemetry-collector Helm chart, OpenTelemetryCollector operator resources, ConfigMaps that embed a config, SDK config files, and OTEL_* settings in Compose files, Kubernetes manifests, Dockerfiles, shell scripts, .env and .properties files. It knows the Collector's defaults (servers on localhost since v0.104.0, TLS on for the gRPC exporter unless insecure: true), accounts for the chart's own default config when it reads Helm values, treats ${env:NAME}, secretKeyRef and SOPS values as references, skips the docs' own placeholders such as YOUR_API_KEY, treats files that one command loads with several --config flags as parts of one config, and never runs the Collector or contacts a backend. It returns BLOCK, REVIEW, or NOT FLAGGED, with the file, line, reason, and a safer approach. Secrets are never printed.
What it checks
BLOCK
- O01: API keys, tokens and passwords written into a Collector or SDK config: exporter headers, auth extensions (bearertokenauth, basic_auth, oauth2client, headers_setter), fields such as api.key or access_token, ${env:NAME:-fallback} defaults and passwords in endpoint URLs
- O02: credentials in OTEL_EXPORTER_OTLP_HEADERS, the otel.exporter.otlp.headers property or -D flags, and secret-named variables on Collector containers (Compose, Kubernetes, Helm extraEnvs, operator spec.env)
- O03: credentials sent to a remote host over plain text (insecure: true, http:// endpoints, OTEL_EXPORTER_OTLP_INSECURE) or with certificate checks off
- O04: configs the Collector refuses to start: pipelines or service.extensions naming undefined components, authenticators or middlewares naming extensions that are not enabled, pipelines with no receivers or exporters, one-sided connectors
REVIEW
- O11: receivers on 0.0.0.0, :: or an empty host with no auth
- O12: the debug exporter with verbosity: detailed in a pipeline
- O13: pipelines without memory_limiter, or with memory_limiter not first
- O14: removed components (logging exporter, jaeger exporters, memory_ballast, opencensus, routing processor, SAPM)
- O15: pprof, zPages or remotetap on every interface
- O16: telemetry to a remote host without TLS or certificate checks, TLS 1.0/1.1, insecure cipher suites
- O17: $NAME or $(NAME) values the Collector does not expand
- O18: credentials written as short words such as changeme or supersecretapikey (weak, or a placeholder never replaced)
What's included
- The scanner (Python 3.9+, standard library only)
- A rules guide with the reason, safer approach and official source for each rule
- A risky and a safe example setup (Collector config and Compose file), and the real report the scanner produces on the risky one
Limits Helm templates are not rendered, configs split over several --config files are recognised only when the command that loads them is in the scanned files or a part has no receivers section, and values filled in from the environment at run time are not known. A host counts as remote when it is a public IP or ends in a public top-level domain. The default config in the official Collector images binds to 0.0.0.0 and gets REVIEW findings by design. JSON configs, Service and Ingress exposure and network policies are not checked. NOT FLAGGED is not a guarantee.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for DevOps & Cloud.
Static check of config text. Helm templates are not rendered, multi-file Collector configs are recognised only from the command that loads them or a part without receivers, and values set from the environment at run time are not known. NOT FLAGGED is not a guarantee.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 4 days ago
- Software
Python
Permissions
Runs one local Python script in the terminal. It reads your project's files, writes nothing, and makes no network calls. The example setup includes clearly fake, inert keys (NOTREAL-EXAMPLE-...) for the scanner to find. Nothing in it is run.