Agent skill · data analytics · jeremylongshore
deepgram-observability
Set up comprehensive observability for Deepgram integrations.
Why this skill is useful
Provides specific Prometheus metrics and structured logging patterns for Deepgram integrations that the AI wouldn't reliably generate on its own.
What it needs
Requires prom-client installed locally. Requires deepgram account access. About 5k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Deepgram Observability Prerequisites An approved metrics/tracing/logging backend, data-retention policy, and on-call owner. Redaction rules that exclude audio, transcript text, API keys, participant identifiers, and other sensitive metadata. Examples Emit aggregate metrics for request count, latency, model, status class, streaming duration, and rate-limit headroom. Trigger a non-sensitive staging failure to verify alert routing, then record the correlation ID and remediation time—never audio samples, transcripts, or credentials. Overview Full observability stack for Deepgram: Prometheus metrics (request counts, latency histograms, audio processed, cost tracking), OpenTelemetry distributed tracing, structured JSON logging with Pino, Grafana dashboard JSON, and AlertManager rules. Four Pillars Pillar Tool What It Tracks -------- ------ ---------------- Metrics Prometheus Request rate, latency, error rate, audio minutes, estimated cost Traces OpenTelemetry End-to-end request flow, Deepgram API span timing Logs Pino (JSON) Request details, errors, audit trail Alerts AlertManager Error rate >5%, P95 latency >10s, rate limit hits Instructions Step 1: Prometheus Metrics Definition Step 2: Instrumented Deepgram Client Step 3: OpenTelemetry Tracing Step 4: Structured Logging with Pino Step 5: Grafana Dashboard Panels Step 6: AlertManager Rules Metrics Endpoint Output Prometheus metrics (6 metrics covering requests, latency, usage, cost) Instrumented Deepgram client with auto-tracking OpenTelemetry distributed tracing with custom spans Structured JSON logging (Pino) Grafana dashboard panel definitions AlertManager rules (5 alerts) Error Handling Issue Cause Solution ------- ------- ---------- Metrics not appearing Registry not exported Check /metrics endpoint High cardinality Too many label values Limit labels to known set Alert storms Thresholds too sensitive Add for: duration, tune values Missing traces OTEL exporter not configured Set OTELEXPORTEROTLPENDPOINT Resources Pro …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/deepgram-observability--0d9b47