Configures trace spans, defines custom metrics, sets up log exporters, and optimizes sampling strategies for OpenTelemetry instrumentation. Use when instrumenting applications with traces, metrics, or logs. Triggers on requests for observability, telemetry, tracing, metrics collection, logging integration, or OTel setup.
98
100%
Does it follow best practices?
Impact
94%
1.38xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Node.js OTel SDK setup
CommonJS flag
100%
100%
Traces exporter enabled
100%
100%
Metrics exporter enabled
100%
100%
Logs exporter enabled
100%
100%
Service name from manifest
100%
100%
gRPC protocol set
100%
0%
Flush on uncaughtException
100%
100%
Flush on unhandledRejection
100%
100%
ProxyTracerProvider unwrapped
100%
100%
Auth header format
100%
100%
No sampler configured
100%
100%
Span, metric, and log instrumentation
Low-cardinality span names
75%
87%
Correct span kind for DB calls
12%
75%
Correct span kind for HTTP client
12%
62%
Headless root span
100%
100%
Exception as log record
20%
100%
Exception attributes on log
25%
100%
Trace correlation in logs
100%
100%
Histogram for latency
100%
100%
UCUM units on metrics
62%
100%
No high-cardinality metric attributes
100%
100%
Dot-separated attribute names
50%
100%
No PII in telemetry
100%
100%
Kubernetes OTel deployment config
k8s.pod.uid via downward API
0%
100%
k8s.pod.name via downward API
100%
100%
k8s.node.name via downward API
100%
100%
k8s.container.name as literal
0%
100%
service.name set
100%
100%
deployment.environment.name set
0%
100%
OTEL_TRACES_EXPORTER=otlp
0%
100%
OTEL_METRICS_EXPORTER=otlp
0%
100%
OTEL_LOGS_EXPORTER=otlp
0%
100%
Auth token from Secret
83%
100%
DaemonSet endpoint reference
100%
100%
service.instance.id unique
0%
100%
cb7cf0d
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.