Browse by category
Find your runtime or use case
AI agent and LLM integrations
Compare implementation guides for model providers, agent frameworks, tool orchestration, retrieval systems, and AI application runtimes.
Open categoryNode.js and TypeScript integrations
Instrument Node.js frameworks, edge runtimes, queues, database clients, loggers, webhooks, and AI applications with server-side events.
Open categoryPython integrations
Instrument Python APIs, workers, database applications, and AI agent frameworks with synchronous or asyncio-safe structured events.
Open categoryBackground job and queue integrations
Instrument schedulers, workers, queues, streams, retries, dead letters, webhooks, and durable workflows from enqueue through final outcome.
Open categoryDatabase integrations
Instrument database clients, ORMs, caches, streams, and application-owned query boundaries without storing raw SQL or sensitive parameters.
Open categoryCloud and infrastructure integrations
Instrument edge functions, serverless jobs, queues, Kubernetes workloads, streams, and cloud AI providers with customer-impact context.
Open categoryApplication framework integrations
Compare request, job, database, and release instrumentation patterns for server frameworks across JavaScript, Python, Elixir, PHP, Java, .NET, and Go.
Open categoryLogging and observability integrations
Connect application loggers, OpenTelemetry context, and framework diagnostics to compact SQL-ready outcome events without duplicating raw telemetry.
Open categoryBrowser and edge integrations
Send approved frontend and edge events through your server. Keep API keys there, check consent, and use route templates instead of raw URLs.
Open categoryBrowse the library
Integration guides
OpenAI agent telemetry
Log OpenAI agent runs, tool calls, model usage, latency, cost, and final outcomes with structured events.
Open guideBrowser JavaScript and Web Vitals telemetry
Send Core Web Vitals and approved frontend result fields through a rate-limited server proxy. Keep the Telemetry API key on the server.
Open guideVercel AI SDK telemetry
Track streaming completions, token usage, retries, latency, and accepted results from AI SDK workflows.
Open guideInngest and Trigger.dev job telemetry
Instrument async workers, scheduled jobs, retries, failures, and dead-letter events with SQL-ready logs.
Open guideStripe webhook telemetry
Debug payment, subscription, invoice, retry, and downstream billing sync behavior without storing webhook bodies.
Open guideSupabase and Postgres app telemetry
Track product workflows, database-adjacent jobs, API routes, and customer-facing failures from server code.
Open guideCloudflare Worker telemetry
Log edge request status, latency, provider failures, cron runs, and queue workers from Cloudflare Workers.
Open guideNode.js and Express structured logging
Instrument Express route outcomes with stable route templates, status codes, request latency, and safe correlation fields.
Open guideNext.js server event analytics
Send SQL-ready events from Next.js route handlers and server actions without exposing an ingestion key to the browser.
Open guidePython and FastAPI structured logging
Capture FastAPI request outcomes and latency with the asynchronous Telemetry client and normalized route names.
Open guideOpenTelemetry context in structured events
Connect Telemetry business events to existing OpenTelemetry traces by recording safe trace and span identifiers at workflow boundaries.
Open guideAWS Lambda structured event monitoring
Track Lambda invocations, cold starts, duration, retries, and business outcomes with compact structured events.
Open guideGo HTTP server structured logging
Add typed request-outcome events to Go HTTP services for route error rates, latency percentiles, and release comparisons.
Open guideRuby on Rails structured event analytics
Record Rails controller and background-workflow outcomes through Telemetry's HTTP API with safe, queryable fields.
Open guideDjango and Celery structured event monitoring
Connect Django request outcomes and Celery task lifecycles with safe identifiers, latency, retries, and final status.
Open guideLaravel structured logging and queue analytics
Send Laravel request, command, queue, and billing outcomes as typed events without exposing application secrets or payloads.
Open guide.NET and Serilog structured event analytics
Add a focused Telemetry outcome event beside Serilog diagnostics for ASP.NET request latency, failures, releases, and customer impact.
Open guideSpring Boot structured event monitoring
Record Spring MVC and scheduled-workflow outcomes through Telemetry's HTTP API with stable routes, latency, status, and trace context.
Open guideTemporal workflow observability
Track Temporal workflow outcomes, activity retries, schedule-to-start latency, and business milestones without recording workflow payloads.
Open guideBullMQ queue monitoring
Measure BullMQ queue wait, execution duration, retries, failures, and dead-letter growth with SQL-ready lifecycle events.
Open guideAWS SQS queue observability
Track SQS message age, receive attempts, processing outcomes, batch behavior, and dead-letter routing without storing message bodies.
Open guideKafka consumer lag and processing analytics
Monitor Kafka consumer outcomes, partition lag, processing latency, retries, and poison-message handling with structured events.
Open guideAnthropic Claude API telemetry
Track Claude API token usage, model, latency, stop reason, errors, cost context, and reviewed product outcomes without storing prompts.
Open guideLangGraph agent observability
Measure LangGraph run outcomes, node and tool failures, retries, checkpoints, human handoffs, latency, and reviewed task quality.
Open guidenode-postgres pool and query telemetry
Instrument node-postgres query fingerprints, connection acquisition, pool pressure, timeouts, transaction outcomes, and database errors without logging SQL parameters.
Open guidePrisma ORM database telemetry
Measure Prisma operation fingerprints, model and method latency, failures, result counts, releases, and database-dependent workflows without collecting raw query parameters.
Open guideKubernetes workload telemetry
Send approved Kubernetes restart, readiness, and rollout fields to Telemetry. Use SQL to compare workloads.
Open guideGoogle Gemini API telemetry
Track Gemini request latency, model usage, tokens, finish reason, errors, and reviewed product outcomes without storing prompts or generated content.
Open guideAmazon Bedrock model telemetry
Measure Bedrock Converse requests by model or inference profile, token usage, latency, stop reason, retries, and business outcome.
Open guideAzure OpenAI Responses telemetry
Track Azure OpenAI deployment usage, token cost, latency, failures, and product outcomes with editable SQL-ready events.
Open guideLangChain agent outcome telemetry
Connect LangChain agent runs and tool outcomes to product-facing cost, reliability, handoff, and acceptance metrics without duplicating raw traces.
Open guidePino structured event analytics
Keep Pino diagnostic logs and send selected completion events to Telemetry to analyze Node.js requests, jobs, and product reliability.
Open guideWinston structured event analytics
Connect Winston application diagnostics to small SQL-ready request, workflow, and job outcomes without duplicating the entire log stream.
Open guideNestJS request and workflow telemetry
Instrument NestJS controllers and providers with normalized route outcomes, latency, errors, releases, and approved account context.
Open guideFlask and SQLAlchemy telemetry
Record Flask request results and SQLAlchemy transaction behavior with approved Python event fields, consistent route templates, and safe error categories.
Open guideSidekiq job telemetry
Track Sidekiq execution outcomes, attempts, queue wait, errors, and releases from server middleware without copying job arguments.
Open guideRedis and node-redis telemetry
Measure Redis command outcomes, latency, cache behavior, reconnects, and bounded error categories alongside node-redis.
Open guideClaude Agent SDK telemetry
Track Claude Agent SDK run outcomes, duration, tool activity, turns, cost, and approved product signals without storing prompts or tool payloads.
Open guidePydantic AI agent telemetry
Measure Pydantic AI run outcomes, validated outputs, retries, tool activity, latency, usage, and product acceptance with safe structured events.
Open guideCrewAI workflow telemetry
Track CrewAI crew and flow outcomes, task counts, handoffs, retries, latency, cost, and accepted results without retaining agent conversations.
Open guideGoogle ADK agent telemetry
Measure Google Agent Development Kit sessions, run outcomes, tool activity, handoffs, latency, and approved product signals with SQL-ready events.
Open guideMastra agent telemetry
Track Mastra agent and workflow outcomes, tool activity, latency, retries, cost, and product acceptance alongside built-in traces and evals.
Open guideLlamaIndex agent telemetry
Track LlamaIndex agent and workflow outcomes, tool activity, latency, retrieval versions, cost, and reviewed quality with structured events.
Open guideDSPy program evaluation telemetry
Measure DSPy program latency, failures, metric scores, optimizer versions, model cost, and accepted outcomes across releases with SQL-ready events.
Open guideAutoGen task flow, state, and timeout monitoring
Track AutoGen task-flow state, timeouts, team and agent outcomes, tool activity, handoffs, latency, failures, cost, and releases with compact structured events.
Open guideSemantic Kernel agent telemetry
Measure Semantic Kernel function and agent outcomes, tool activity, model usage, latency, cost, and releases alongside OpenTelemetry traces.
Open guideMCP server and tool telemetry
Track Model Context Protocol tool outcomes, latency, errors, approvals, retries, clients, and releases without storing arguments or returned content.
Open guideRabbitMQ queue telemetry
Track RabbitMQ publish confirmation, delivery, acknowledgement, redelivery, queue wait, retries, and dead-letter outcomes with structured events.
Open guideMySQL query and pool telemetry
Track normalized MySQL operations, pool wait, transaction outcomes, controlled error categories, and release regressions without storing raw SQL or parameters.
Open guideMongoDB operation telemetry
Track named MongoDB operations, latency, result counts, retries, transaction outcomes, and release regressions without collecting documents or query values.
Open guideGoogle Cloud Run telemetry
Track Cloud Run request and job outcomes, cold-start context, instance concurrency, retries, latency, and releases with application-owned structured events.
Open guideGoogle Cloud Pub/Sub telemetry
Track Pub/Sub publish, delivery, acknowledgement, redelivery, ordering, queue age, and dead-letter outcomes with stable message identifiers.
Open guideAzure Functions telemetry
Track Azure Functions HTTP, timer, queue, and event-trigger outcomes with invocation, retry, latency, release, and customer-impact context.
Open guideAzure Service Bus telemetry
Track Azure Service Bus sends, receives, lock renewal, settlement, redelivery, deferral, and dead-letter outcomes without collecting message bodies.
Open guideOpenAI Responses API telemetry
Measure OpenAI Responses API latency, token usage, tool activity, failures, and downstream outcomes without collecting prompts or generated content.
Open guideLiteLLM gateway and SDK telemetry
Track LiteLLM provider routing, retries, fallbacks, token usage, latency, cost estimates, and accepted outcomes across a controlled model gateway.
Open guideElixir Phoenix telemetry integration
Listen for Phoenix request lifecycle events and forward the final request result with approved fields. Exclude connection data, parameters, and exception text.
Open guideAWS ECS and Fargate telemetry integration
Add ECS task family, revision, availability zone, and release context to application outcomes using the local task metadata endpoint.
Open guideGitHub Actions workflow telemetry integration
When a GitHub Actions workflow finishes, send its run, attempt, job, conclusion, duration, and release fields.
Open guiden8n workflow telemetry
Use the n8n HTTP Request node to send approved fields for workflow completion, failure, retries, item counts, and downstream delivery results to Telemetry.
Open guideHow to choose
Choose a guide for your next task
Choose where to add events
Choose the framework or provider that owns the final request, job, model call, or webhook outcome.
Keep product context
Include approved feature, route, team, and outcome fields so you can identify which customers a failure affected.
Exercise failure paths
Send success, failure, timeout, and retry examples before relying on an alert or dashboard.
Start with one workflow
Use the setup prompt, then check that your events arrive
Create a free API key and choose a guide for your application. Ask your agent to run the workflow and confirm that its events arrive in Telemetry.