Instrument after the framework resolves the outcome
Use middleware, exception filters, response hooks, or handler wrappers that can observe the final status, duration, and error category.
Selection framework
Log where the final result is known
Separate transport success from product success
A 200 response can still mean the workflow was rejected or is incomplete. Record the business result where your app knows what happened.
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
Use the same field definitions across services
- 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 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 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
Setup guide with source links
Node.js and Express structured logging
Instrument Express route outcomes with stable route templates, status codes, request latency, and safe correlation fields.
Open guideSetup guide with source links
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 guideSetup guide with source links
NestJS request and workflow telemetry
Instrument NestJS controllers and providers with normalized route outcomes, latency, errors, releases, and approved account context.
Open guideSetup guide with source links
Python and FastAPI structured logging
Capture FastAPI request outcomes and latency with the asynchronous Telemetry client and normalized route names.
Open guideSetup guide with source links
Django and Celery structured event monitoring
Connect Django request outcomes and Celery task lifecycles with safe identifiers, latency, retries, and final status.
Open guideSetup guide with source links
Flask and SQLAlchemy telemetry
Record Flask request results and SQLAlchemy transaction behavior with approved Python event fields, consistent route templates, and safe error categories.
Open guideSetup guide with source links
Elixir 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 guideSetup guide with source links
Laravel structured logging and queue analytics
Send Laravel request, command, queue, and billing outcomes as typed events without exposing application secrets or payloads.
Open guideSetup guide with source links
.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 guideSetup guide with source links
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 guideSetup guide with source links
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.