Instrument after the framework resolves the outcome
Use terminal middleware, exception filters, response hooks, or handler wrappers where status, duration, and controlled error category are known.
Selection framework
Choose the boundary that knows the result
Separate transport success from product success
A 200 response can still represent a rejected or incomplete workflow. Add the bounded business outcome at the layer that owns it.
Use stable names across releases
Record route templates, named operations, and releases instead of raw URLs, function source, request bodies, or arbitrary exception messages.
Shared event contract
Keep the first schema interoperable
- route_template, method, status, outcome, duration_ms, and release
- request_id, account_id, environment, runtime, and controlled error_type
- database duration, queue handoff, dependency, and business outcome where known
Adapt these fields to the workflow, but keep units, status categories, identifiers, and ownership explicit before several services depend on the same table.
Verification
Exercise failure paths before alerts
- 1Exercise one success, validation failure, unhandled exception, and timeout.
- 2Confirm route names are templated and sensitive request data is excluded.
- 3Compare recorded duration and status with the framework response.
- 4Restart the runtime and verify pending telemetry cannot block shutdown indefinitely.
Implementation guides
Match the framework, provider, or runtime
Sourced implementation guide
Node.js and Express Structured Logging
Instrument Express route outcomes with stable route templates, status codes, request latency, and safe correlation fields.
Open guideSourced implementation guide
Next.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 guideSourced implementation guide
NestJS Request and Workflow Telemetry
Instrument NestJS controllers and providers with normalized route outcomes, latency, errors, releases, and approved account context.
Open guideSourced implementation guide
Python and FastAPI Structured Logging
Capture FastAPI request outcomes and latency with the asynchronous Telemetry client and normalized route names.
Open guideSourced implementation guide
Django and Celery Structured Event Monitoring
Connect Django request outcomes and Celery task lifecycles with safe identifiers, latency, retries, and terminal status.
Open guideSourced implementation guide
Flask and SQLAlchemy Telemetry
Measure Flask request outcomes and SQLAlchemy transaction behavior with bounded Python events, stable route templates, and safe error categories.
Open guideSourced implementation guide
Elixir Phoenix Telemetry Integration
Attach to Phoenix request lifecycle events and forward a bounded terminal request outcome without copying connection data, parameters, or exception text.
Open guideSourced implementation guide
Laravel Structured Logging and Queue Analytics
Send Laravel request, command, queue, and billing outcomes as typed events without exposing application secrets or payloads.
Open guideSourced implementation 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 guideSourced implementation guide
Spring 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 guideSourced implementation guide
Go HTTP Server Structured Logging
Add typed request-outcome events to Go HTTP services for route error rates, latency percentiles, and release comparisons.
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.