OpenTelemetry Integrator Skill
SkillMonitoring & opsIntegrate OpenTelemetry tracing and metrics into SDKs
Instructions available. Your AI can read the instructions. Execution depends on the setup they require.
Account requirements not reviewed. Check the skill instructions before use; ahel provides instructions and does not run this skill.
Add ahel to your AI once: Claude, ChatGPT, Cursor, Claude Code or Codex. Then ask it to use this.
Then ask your AI: use the OpenTelemetry Integrator Skill skill
What this skill tells your AI
The instructions your AI receives, as published by a5c-ai/babysitter in library/specializations/sdk-platform-development/skills/opentelemetry-integrator/SKILL.md and read by ahel’s review.
Overview
This skill integrates OpenTelemetry observability into SDKs, providing distributed tracing, metrics collection, and context propagation for comprehensive API monitoring.
Capabilities
- Add tracing spans to SDK operations
- Export metrics (latency, errors, throughput)
- Configure context propagation (W3C Trace Context)
- Support multiple exporters (OTLP, Jaeger, Zipkin)
- Implement custom span attributes
- Configure sampling strategies
- Add semantic conventions for SDK operations
- Support baggage propagation
Target Processes
- Observability Integration
- Telemetry and Analytics Integration
- Logging and Diagnostics
Integration Points
- OpenTelemetry SDKs (all languages)
- Jaeger for distributed tracing
- Prometheus for metrics
- Grafana for visualization
- Cloud observability platforms
Input Requirements
- Tracing requirements
- Metrics to collect
- Exporter configurations
- Sampling strategy
- Semantic convention mappings
Output Artifacts
- OpenTelemetry instrumentation
- Custom span definitions
- Metrics collectors
- Exporter configurations
- Propagator setup
- Sampling configuration
Usage Example
skill:
name: opentelemetry-integrator
context:
tracing:
enabled: true
propagator: w3c-trace-context
sampling: parentBased
sampleRate: 0.1
metrics:
enabled: true
exportInterval: 30s
metrics:
- sdk.request.duration
- sdk.request.count
- sdk.error.count
exporters:
traces: otlp
metrics: prometheus
serviceName: "my-sdk"
Best Practices
- Follow OpenTelemetry semantic conventions
- Use appropriate sampling rates
- Propagate context across boundaries
- Include useful span attributes
- Avoid high-cardinality attributes
- Configure exporters for production
Signals
- GitHub stars
- 2k
- Forks
- 112
- Last commit
- Sep 2026
Advanced
- Item type
- skill
- Key
opentelemetry-integrator- Source
- github.com/a5c-ai/babysitter
More in Monitoring & ops
Skill · anthropics
More in Monitoring & opsagent-eval
Skill · affaan-m
More in Monitoring & opsdashboard-builder
Skill · affaan-m
More in Monitoring & opsbabysit
Skill · thedotmack
More in Monitoring & opseng-runbook
Skill · nexu-io
More in Monitoring & opsweekly-update
Skill · nexu-io
More in Monitoring & ops