OpenTelemetry streaming

Stream events to Datadog, Grafana, and OpenTelemetry.

Your customers can receive events as OpenTelemetry traces and send them to Datadog, Grafana, or any OTel-compatible backend, where they already run their observability.
Try for freeRead the docs

Observability for your products' events.

Teams already monitor their systems in an observability platform. When the events from your API arrive there as traces, they can search, chart, and alert on them with the tools they use every day.

Search and chart your events

Customers query your events by type or field, and graph them next to their own metrics.

One less dashboard to check

Your events sit next to their logs and metrics, so there's no separate tool to log in to.

Alert on your events

Customers set alerts on your events with the same monitors they use for the rest of their stack.

Supported observability platforms

Each event arrives as a trace. Send it to Datadog, Grafana, or any collector that speaks OpenTelemetry.

Related events in one trace

Each event becomes a span named after its event type, with the payload as attributes. A short transformation can take the timing from the payload and group related events, like the steps of one invoice, into a single trace.

Your API sends
{
  "eventType": "invoice.paid",
  "payload": {
    "id": "inv_123",
    "amount": 1000
  }
}
Datadog · Trace inv_123
Span0s1s2s3s
invoice.created
payment.attempted
payment.succeeded
invoice.paid
invoice.paid · attributesidinv_123amount1000

More Use Cases

See all Advanced Destinations
Data WarehousingStream events to S3, Snowflake, Redshift, and other storage.Polling and FIFOLet customers poll for events, or receive them in strict order.Message QueuesDeliver events to SQS, EventBridge, and RabbitMQ.

Which observability platforms are supported?

Any backend that accepts OTLP traces. Svix has ready-made connectors for Datadog, Grafana Cloud, New Relic, and OpenTelemetry collectors, and platforms like Coralogix work by adding the headers they require.

What does my customer need to configure?

The OTLP traces URL from their provider, usually their OTLP endpoint followed by /v1/traces, plus any headers it requires, like the dd-api-key header for Datadog.

Can spans use the times from the event itself?

Yes. By default a span is stamped with the time Svix sends it. A transformation can read the start and end times from the payload instead, so the trace shows when things actually happened.

Can related events show up in the same trace?

Yes. A transformation can give spans a shared trace key and point a span at its parent, so related events, like the steps of one order, appear together as a single trace.

Do I need to change how I send events?

No. You keep calling the same message API. Your customers configure how they want to receive them in the Application Portal.

Start sending webhooks today, no credit card required.

Get started for freeRead the docs