Distributed Tracing

Follow every request across every service. Find latency, failures, and broken dependencies with precision — not guesswork.

Osuite trace waterfall for the web HTTP GET behind GET /api/orders/:orderId, which ended in a 504: spans run from web through gateway to orders, where the SELECT orders span fails. The span panel shows the error timeout exceeded when trying to connect and the db.statement SELECT * FROM orders WHERE id = $1 LIMIT 1
orders can't get a Postgres connection
The query that was waiting
  1. orders can't get a Postgres connection
  2. The query that was waiting

See exactly what happened, and exactly where.

End-to-end visibility

Trace every request across your microservices — from a frontend click to the database query that served it

Powerful analysis tools

Flamegraphs, waterfalls, span lists, and related logs to diagnose any issue

Smart ingestion control

Osuite Ingestion Pipeline with tail-based sampling so you capture what matters without paying for everything

Waterfall

Follow one request to the span that failed

The failing request from the demo incident, span by span. Hover or focus a span to read its attributes, then switch on the critical path to see where the time went.

Traces9c7ed92e

webHTTP GETError

Duration
8.35s
Spans
20
Services
6
Errors
6
Status
504 Error
Trace ID
9c7ed92eb31b7689727afc425443b349
HTTP GETweb
8.35s, status ERROR
GET /api/orders/:orderIdgateway
8.07s, status ERROR
GET /orders/{order_id}gateway
7.80s, status ERROR
GET /orders/:orderIdorders
4.74s, status ERROR
request handler - /orders/:orderIdorders
4.74s, status ERROR
SELECT ordersorders
4.32s, status ERROR: timeout exceeded when trying to connect
GET /payments/{payment_id}orders
37.1ms, status UNSET
GET /payments/{payment_id}payments
31.9ms, status UNSET
SELECT paymentspayments
1.92ms, status UNSET
SELECT refundspayments
4.73ms, status UNSET
GET /shipments/{shipment_id}orders
37.6ms, status UNSET
GET /shipments/:shipmentIdshipping
32.8ms, status UNSET
request handler - /shipments/:shipmentIdshipping
32.1ms, status UNSET
SELECT shipmentsshipping
1.97ms, status UNSET
UPDATE shipmentsshipping
1.13ms, status UNSET
GET /users/{user_id}orders
21.4ms, status UNSET
GET /users/:userIdusers
18.1ms, status UNSET
request handler - /users/:userIdusers
17.7ms, status UNSET
SELECT usersusers
5.53ms, status UNSET
SELECT sessionsusers
5.80ms, status UNSET

Hover or focus a span · ↑ ↓ Home End to move · ← → parent and child

GET /api/orders/:orderId · 504

Full Trace Visualization

  • Waterfall view to see the full timeline of a request across every service and span
  • Flamegraph view to instantly identify where time is being spent in deep call stacks
  • Span list view for granular inspection of every operation in a trace
Osuite span panel for the failing SELECT orders span: an error box reading timeout exceeded when trying to connect, above the db.statement SELECT * FROM orders WHERE id = $1 LIMIT 1
Why the span failed
The exact query it ran
  1. Why the span failed
  2. The exact query it ran

Logs in Trace Context

  • Open the Related logs panel on any span to read the logs that span emitted, without leaving the trace
  • Filter by trace ID to see every log line from a single request, in order
  • Read span timing and log context together to pinpoint the root cause of a slow or failing request
Osuite trace view on its Logs tab: the logs that share the failing trace's ID, newest first, with gateway 504 and context deadline errors above the orders error timeout exceeded when trying to connect
The pool timeout, in this trace's logs
  1. The pool timeout, in this trace's logs

Service Dependency Map

  • Automatically discover and visualize dependencies between all your services
  • See which services call which, with each edge's width showing its request rate
  • Instantly understand blast radius when a service degrades or goes down
Osuite service map zoomed on orders: gateway calls cart and orders, orders calls users, payments and shipping, and the edges into and out of orders are dashed red. The orders node reads 3.14 req/s at 10.3% errors
orders at 10.3% errors
  1. orders at 10.3% errors

Osuite Ingestion Pipeline

  • Tail-based sampling to make capture decisions after a trace completes — keeping errors and outliers, dropping the noise
  • Sampling rules are configured for your account by the Osuite team — no collector wrestling on your side
  • Reduce ingestion costs without losing visibility into what actually matters
gateway orders payments shipping Tail-based sampling decides once the trace is complete Errors every one kept Slow requests every one kept Routine a sample kept Routine the rest dropped gateway orders payments shipping Tail-based sampling decides once the trace is complete Errors every one kept Slow requests every one kept Routine a sample kept Routine the rest dropped
An illustration of tail-based sampling. Osuite ingests every trace by default; on request, the Osuite team sets sampling rules for your account on the ingestion side. How sampling works

Frequently Asked Questions

What is tail-based sampling and why does it matter?
Unlike head-based sampling, tail-based sampling waits until a trace is complete before deciding whether to keep it. This means you always retain traces with errors, high latency, or anomalies — and drop the routine, healthy ones that add cost without insight.
How does Osuite's Ingestion Pipeline differ from standard OTel sampling?
Osuite applies tail-based sampling on the ingestion side, so the keep-or-drop decision is made once a trace is complete and its outcome is known. The Osuite team sets the rules up for your account — tell us what you need kept and we configure it.
Do I need to instrument my services specifically for Osuite?
No. Osuite is OpenTelemetry native. Any service already emitting OTel traces works immediately, across any language or framework.
Can I correlate traces with logs and metrics?
Yes. Traces in Osuite are fully linked to related logs and metrics. From any span, you can jump to the correlated log lines or infrastructure metrics without leaving the trace view.

See what Osuite can do for your team

Get a personalized walkthrough of the platform and a cost comparison against your current observability stack.

No commitment. No sales pressure. Just a real look at the platform.