InfraWatchdogradar
Trace journey

Follow one request across every service on a single timeline.

Drop in a request id, trace id, or customer id. We fan it across every log group in the service and stitch the matches together. The story of one request — readable in one screen.

What you'll actually see
trace · req_a1b2c3 · acme-api · last 1h6 events · 4 log groups
  1. 14:21:04.812
    /ecs/acme-api/web
    POST /v1/jobs req_a1b2c3 user=cust_8821
  2. 14:21:04.901
    /ecs/acme-api/payments
    PaymentProcessor.charge req_a1b2c3 amount=4900
  3. 14:21:05.044
    /ecs/acme-api/fraud
    fraud.score req_a1b2c3 score=0.04 ALLOW
  4. 14:21:16.402
    /ecs/acme-api/payments
    WARN req_a1b2c3 stripe webhook timeout 11400ms
  5. 14:21:16.408
    /ecs/acme-api/web
    ERROR req_a1b2c3 5xx returned to client
  6. 14:21:16.502
    /aws/rds/acme-api-pg
    rollback transaction req_a1b2c3

What changes for the on-call engineer

One ID, one screen

No more 6 Logs Insights tabs. Paste an ID, get the journey.

Customer support gold

"Why did this user see an error?" — answered in 30 seconds, not a Slack thread.

Cross-log-group by default

Fans across every log group in the service. You don't pick — Radar already knows.

How it works

step · 01

Pick a service

Service map already groups your log groups into the services you care about.

step · 02

Paste an ID

Request id, trace id, customer id, request id — anything that appears in your logs.

step · 03

Read the timeline

We render the events in order with the log group, stream, and message — copy-paste-ready.

Pairs well with

Service map

What lets trace know which log groups to fan across.

Natural-language search

Same data, different question shape.

Resolve incidents in 30 seconds, not 30 minutes.

Connect your AWS account in read-only mode and let Radar take the next page.