Skip to content
Telemetry
Integration collection

Logging and observability integrations

Connect application loggers, OpenTelemetry context, and framework diagnostics to compact SQL-ready outcome events without duplicating raw telemetry.

Reviewed by the Telemetry product team on . We checked where the code runs, shared event fields, verification steps, and the linked implementation guides. Who reviews this page

5 implementation guides

Every guide includes a server-side snippet, delivery and privacy boundaries, a verification query, related SQL, and links to upstream documentation.

Browse guides

Selection framework

Log where the final result is known

Keep logs and traces in the tools you use for them

Send one event when a request, job, or workflow finishes. Keep the individual log lines and spans in your debugging tools.

Correlate without copying payloads

Use an approved trace or request ID to find the matching record in each system. Exclude stack traces, log messages, span attributes, and customer content.

Use consistent fields in application code

Convert logger levels and exceptions into controlled outcomes and error categories before the event reaches an analytical table.

Shared event contract

Use the same field definitions across services

  • event_name, service, environment, release, status, and duration_ms
  • approved trace_id, request_id, account_id, and controlled error_type
  • operation, dependency, retry_count, and final business outcome

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

  1. 1Compare one event with its originating log or trace using an approved identifier.
  2. 2Confirm an exception does not copy stack text, parameters, or credentials.
  3. 3Check that one logical outcome does not become one event per log line or span.
  4. 4Query outcome and error trends by service and release.

Implementation guides

Match the framework, provider, or runtime

Setup guide with source links

Pino structured event analytics

Keep Pino diagnostic logs and send selected completion events to Telemetry to analyze Node.js requests, jobs, and product reliability.

Open guide
Setup guide with source links

Winston structured event analytics

Connect Winston application diagnostics to small SQL-ready request, workflow, and job outcomes without duplicating the entire log stream.

Open guide
Setup 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 guide
Setup 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 guide
Setup 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 guide

Verify 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.

Start free