Agent skill · data analytics · jeremylongshore
intercom-observability
Use when you need production monitoring for an Intercom integration — instrumenting API calls with metrics and traces, standing up dashboards, or wiring alerts for error rate, latency, and rate-limit health. Set up observability for Intercom integrations with Prometheus metrics, OpenTelemetry traces, structured logging, and alert rules. Trigger with phrases like "intercom monitoring", "intercom metrics", "intercom observability", "monitor intercom", "intercom alerts", "intercom tracing".
Why this skill is useful
Adds executable code snippets for Prometheus metrics, OpenTelemetry tracing, and structured logging specifically for Intercom integrations.
What it needs
Requires grafana, opentelemetry, pino, prometheus installed locally. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Intercom Observability Overview Comprehensive observability for Intercom integrations covering Prometheus metrics, OpenTelemetry traces, structured logging, and alert rules for error rates, latency, and rate-limit usage. Read this page for the workflow and shape of each layer, then drill into references/implementation.md for the full, copy-pasteable code and references/examples.md for end-to-end worked scenarios. Prerequisites Prometheus or compatible metrics backend OpenTelemetry SDK (optional, for tracing) Pino or similar structured logger Grafana or alerting system Instructions Build the six observability layers in order. Each step below is the summary and the essential skeleton — the complete implementation for every step lives in references/implementation.md. Step 1: Prometheus metrics Define five instruments on a shared Registry: a request counter, a duration histogram, an error counter, a rate-limit gauge, and a webhook counter. Label by endpoint/method/status (never by unbounded IDs — see Error Handling). Full metric set → references/implementation.md, Step 1. Step 2: Instrumented client wrapper Wrap IntercomClient in a Proxy that times every service method, increments the success/error counters, records error/status codes on IntercomError, and zeros the rate-limit gauge on a 429 — so instrumentation is automatic for all endpoints. Full proxy → references/implementation.md, Step 2. Step 3: Structured logging Configure Pino with a contact serializer that emits only id/role and never logs email, name, or phone. Add logIntercomOp and logWebhook helpers for consistent operation/webhook log lines. Full logger → references/implementation.md, Step 3. Step 4: OpenTelemetry tracing Wrap calls in tracedIntercomCall, which opens a per-operation intercom. span, sets OK/ERROR status, records exceptions, and attaches statuscode/errorcode/requestid attributes on Intercom errors. Full tracer → references/implementation.md, Step 4. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/intercom-observability