o11y-dev/opentelemetry-skill
Expert OpenTelemetry guidance for collector configuration, pipeline design, and production telemetry instrumentation across Kubernetes, ECS, serverless, and standalone deployments. Use when configuring collectors, designing pipelines, instrumenting applications, implementing sampling, managing cardinality, securing telemetry, writing OTTL transformations, or setting up AI coding agent observability (Claude Code, Codex, Gemini CLI, GitHub Copilot).
94
98%
Does it follow best practices?
Impact
94%
1.34xAverage score across 18 eval scenarios
Passed
No known issues
task.mdevals/scenario-13/
Deploy the OpenTelemetry Collector as a Gateway (Deployment) in Kubernetes to receive telemetry from distributed applications. The collector should:
- Run as a Deployment (not DaemonSet) with configurable replicas
- Use a load balancer service for distributing traffic
- Implement a loadbalancing exporter to route traces by trace ID for tail sampling
- Configure resource requests and limits appropriate for centralized processing
- Use persistent queues for resilience against backend outages
.claude-plugin
.codex-plugin
.cursor-plugin
.github
scripts
docs
evals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5
scenario-6
scenario-7
scenario-8
scenario-9
scenario-10
scenario-11
scenario-12
scenario-13
scenario-14
scenario-15
scenario-16
scenario-17
scenario-18
references