Observability Instrumentation

IntermediaopsContexto mínimo: 32K

Adds production-grade observability to a codebase by instrumenting it with structured logs, metrics, and distributed traces. Recommends span boundaries, cardinality-safe labels, and OpenTelemetry conventions, then generates the wiring code and dashboards needed to make a service debuggable in production.

observabilityopentelemetrytracingmetricsloggingmonitoring

Casos de uso

  • Adding OpenTelemetry tracing to an existing service
  • Defining metrics and SLIs for a new API
  • Reducing metric cardinality that is blowing up costs
  • Standardizing structured logging across microservices

Prompt de ejemplo

Instrument this Express.js service with OpenTelemetry. Add distributed tracing around the
route handlers and database calls, emit request-rate/error-rate/latency metrics, and switch
console logs to structured JSON logs with a trace_id field. Explain span boundaries and any
cardinality risks in the labels you choose.

```
[paste service code here]
```

Modelos recomendados

claude-opus-4-8gpt-5-6-solgemini-3-5-prodeepseek-v4

Herramientas compatibles

claude-codecursorkiroany

Modalidades

Entrada: code, text
→
Salida: code, text

Skills relacionadas

log-analysisincident-responseperformance-optimization

Autor

OpenModels Community

@openmodelsrun