signal-choice-advisor

What problem does it solve?

It helps you avoid instrumenting the wrong telemetry type by translating vague “what should we observe?” requests into the correct OTel signal choice and naming strategy.

Core Features & Use Cases

• Signal type decision support: Recommends Counter, Histogram, UpDownCounter, Observable Gauge, Span, structured logs, or resource attributes based on the stated goal.
• Cardinality and anti-pattern guardrails: Prevents common mistakes like embedding service names or high-cardinality identifiers in metric dimensions.
• OTel semconv-first guidance: Encourages standard conventions before inventing custom names, with a workflow to verify semantic correctness.
• Language-appropriate implementation pointers: Prompts you to follow up with the relevant OTel language skill for a concrete implementation sketch.

Quick Start

Ask: “Should I add a metric or a span for the duration of X, and which instrument type should I use?” and the skill will produce a reasoned recommendation plus an implementation direction.