Start where the workload runs
Prefer stable service, workload, queue, and route names over ephemeral pod IDs, raw resource paths, or provider payloads.
Selection framework
Log where the final result is known
Pair resource pressure with demand
CPU, memory, restarts, lag, and throttling need request or job volume plus release context before they support a capacity decision.
Keep using your infrastructure and tracing tools
Keep infrastructure and trace details in your existing monitoring tools. Send selected application outcomes to Telemetry and use SQL to find affected customers.
Shared event contract
Use the same field definitions across services
- service, region, environment, release, status, and duration_ms
- provider, runtime, workload, queue, dependency, and controlled error_type
- request volume, resource saturation, retry count, and customer-impact fields
Adapt these fields to your workflow. Document units, allowed statuses, and identifiers before several services write to the same table. Name the team responsible for the schema.
Verification
Exercise failure paths before alerts
- 1Exercise one healthy deployment and one controlled provider or workload failure.
- 2Check that region, release, service, and runtime fields use the expected values.
- 3Test retry and timeout behavior without recursive telemetry failures.
- 4Compare infrastructure changes with request, job, or product outcomes.
Implementation guides
Match the framework, provider, or runtime
Setup guide with source links
Cloudflare Worker telemetry
Log edge request status, latency, provider failures, cron runs, and queue workers from Cloudflare Workers.
Open guideSetup guide with source links
AWS Lambda structured event monitoring
Track Lambda invocations, cold starts, duration, retries, and business outcomes with compact structured events.
Open guideSetup guide with source links
AWS 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 guideSetup guide with source links
AWS SQS queue observability
Track SQS message age, receive attempts, processing outcomes, batch behavior, and dead-letter routing without storing message bodies.
Open guideSetup guide with source links
Google 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 guideSetup guide with source links
Google Cloud Pub/Sub telemetry
Track Pub/Sub publish, delivery, acknowledgement, redelivery, ordering, queue age, and dead-letter outcomes with stable message identifiers.
Open guideSetup guide with source links
Azure Functions telemetry
Track Azure Functions HTTP, timer, queue, and event-trigger outcomes with invocation, retry, latency, release, and customer-impact context.
Open guideSetup guide with source links
Azure Service Bus telemetry
Track Azure Service Bus sends, receives, lock renewal, settlement, redelivery, deferral, and dead-letter outcomes without collecting message bodies.
Open guideSetup guide with source links
Kafka consumer lag and processing analytics
Monitor Kafka consumer outcomes, partition lag, processing latency, retries, and poison-message handling with structured events.
Open guideSetup guide with source links
Kubernetes workload telemetry
Send approved Kubernetes restart, readiness, and rollout fields to Telemetry. Use SQL to compare workloads.
Open guideSetup guide with source links
Amazon Bedrock model telemetry
Measure Bedrock Converse requests by model or inference profile, token usage, latency, stop reason, retries, and business outcome.
Open guideSetup guide with source links
Azure OpenAI Responses telemetry
Track Azure OpenAI deployment usage, token cost, latency, failures, and product outcomes with editable SQL-ready events.
Open guideSetup guide with source links
Google Gemini API telemetry
Track Gemini request latency, model usage, tokens, finish reason, errors, and reviewed product outcomes without storing prompts or generated content.
Open guideSetup guide with source links
OpenTelemetry context in structured events
Connect Telemetry business events to existing OpenTelemetry traces by recording safe trace and span identifiers at workflow boundaries.
Open guideVerify one end-to-end workflow first
Create a free API key, choose the closest runtime guide, and send one known success and failure before expanding coverage.