OpenParable
Skip to content
← Back to skills

Opentelemetry Integrator

DevOps & Security
opentelemetry-integrator

Opentelemetry Integrator is an Agent Skill for devops & security published in the a5c-ai/babysitter repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Integrate OpenTelemetry tracing and metrics into SDKs

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/a5c-ai/babysitter/blob/HEAD/library/specializations/sdk-platform-development/skills/opentelemetry-integrator/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/opentelemetry-integrator, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

OpenTelemetry Integrator Skill

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

  1. Follow OpenTelemetry semantic conventions
  2. Use appropriate sampling rates
  3. Propagate context across boundaries
  4. Include useful span attributes
  5. Avoid high-cardinality attributes
  6. Configure exporters for production