Telemetry
Integration collection

Logging and Observability Telemetry 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 . Runtime boundaries, shared event fields, verification workflow, and upstream implementation sources. Review standards and ownership

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

Choose the boundary that knows the result

Keep raw diagnostics in their specialist system

Do not mirror every log line or span. Send one bounded event when a request, job, or workflow reaches an outcome worth analyzing with SQL.

Correlate without copying payloads

Use an approved trace or request identifier to pivot between systems while excluding stack traces, log messages, span attributes, and customer content.

Normalize at the application boundary

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

Shared event contract

Keep the first schema interoperable

  • 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 terminal business outcome

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

  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

Sourced implementation guide

Pino Structured Event Analytics

Pair Pino diagnostic logs with bounded Telemetry outcome events for Node.js request, job, and product reliability analysis.

Open guide
Sourced implementation guide

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
Sourced implementation guide

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
Sourced 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 guide
Sourced 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 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