otel_instrument

You can route OpenTelemetry work by describing your telemetry task in plain language. The system analyzes your intent and delegates the request to the appropriate sub-skill, covering instrumentation, collectors, semantic conventions, or OTTL transformations.

Semantic convention routing directs OpenTelemetry observability requests to a specialized sub-skill. It identifies whether your task involves tracing, metrics, logging, or semantic standards, and safely delegates the work instead of attempting a generic solution.

Yes, you can use it for both OpenTelemetry SDK instrumentation and Collector pipelines. It identifies your specific observability requirements and routes the configuration work to the appropriate dedicated sub-skill for safe delegation.

To apply OTTL transformations across application services, the orchestrator identifies your processing intent and routes the request to a specialized OTTL sub-skill. This ensures your telemetry data transformations are handled by targeted logic rather than generic configurations.

When an OpenTelemetry request matches multiple sub-skills, the system applies first-match routing with safe fallbacks. It prioritizes the most relevant intent identified in your request and provides clear delegation to prevent conflicting telemetry configurations.