Search logs, jump to the trace

Logs arrive structured and linked to their trace. Any result opens the request that wrote it.

Start free trial View on GitHub

The surface

Filter by severity, service and attribute

Filter counts are computed for the time range you picked.

Structured log search with severity facets and attribute filters down the left rail
/logs severity >= WARN
signal
logs
transport
OTLP · no agent
severity
TRACE · DEBUG · INFO · WARN · ERROR · FATAL
filters
body · resource.* · log.*
joins.on
trace_id · span_id
buckets
5 min

In motion

Live tail

New lines stream in, tagged with service and severity. Same data as search.

logs · stream LIVE
12:04:18 INFO edge GET /api/orders/8421 200 412ms
12:04:18 INFO orders-api load_order order_id=8421 366ms
12:04:18 DEBUG auth verify_jwt iss=auth.maple.dev 38ms
12:04:18 INFO postgres SELECT line_items rows=12 158ms
12:04:18 INFO shipping rate_quote carrier=ups 96ms
12:04:18 WARN fedex-api POST /rates retried (1/3) 72ms
12:04:18 INFO redis SET order:8421:rate ttl=3600 14ms
12:04:19 INFO edge GET /api/cart 200 94ms
12:04:19 INFO cart-svc load_cart user=u_4109 58ms
12:04:19 DEBUG feature-flag evaluate fast_checkout=false
12:04:19 ERROR payments stripe.charge declined card=v•••4242 204ms
12:04:19 WARN payments fallback to authorize_only flow
12:04:19 INFO kafka produce orders.canceled offset=98041
12:04:20 INFO edge POST /webhooks/stripe 200 26ms
12:04:20 INFO events dispatch payment.failed → ops
12:04:20 DEBUG scheduler reschedule retry_at=12:04:25
12:04:20 INFO edge GET /api/inventory 200 41ms
12:04:20 INFO inventory lookup sku=SKU-9081 region=iad 23ms
12:04:20 WARN inventory stock low sku=SKU-9081 qty=3
12:04:21 INFO search query "red shoes" hits=412 82ms
12:04:21 INFO edge GET /api/recos 200 67ms
12:04:21 DEBUG recos model=v3.2 cohort=A2
12:04:21 INFO edge POST /api/feedback 201 18ms
12:04:21 INFO analytics track event=checkout_started
12:04:18 INFO edge GET /api/orders/8421 200 412ms
12:04:18 INFO orders-api load_order order_id=8421 366ms
12:04:18 DEBUG auth verify_jwt iss=auth.maple.dev 38ms
12:04:18 INFO postgres SELECT line_items rows=12 158ms
12:04:18 INFO shipping rate_quote carrier=ups 96ms
12:04:18 WARN fedex-api POST /rates retried (1/3) 72ms
12:04:18 INFO redis SET order:8421:rate ttl=3600 14ms
12:04:19 INFO edge GET /api/cart 200 94ms
12:04:19 INFO cart-svc load_cart user=u_4109 58ms
12:04:19 DEBUG feature-flag evaluate fast_checkout=false
12:04:19 ERROR payments stripe.charge declined card=v•••4242 204ms
12:04:19 WARN payments fallback to authorize_only flow
12:04:19 INFO kafka produce orders.canceled offset=98041
12:04:20 INFO edge POST /webhooks/stripe 200 26ms
12:04:20 INFO events dispatch payment.failed → ops
12:04:20 DEBUG scheduler reschedule retry_at=12:04:25
12:04:20 INFO edge GET /api/inventory 200 41ms
12:04:20 INFO inventory lookup sku=SKU-9081 region=iad 23ms
12:04:20 WARN inventory stock low sku=SKU-9081 qty=3
12:04:21 INFO search query "red shoes" hits=412 82ms
12:04:21 INFO edge GET /api/recos 200 67ms
12:04:21 DEBUG recos model=v3.2 cohort=A2
12:04:21 INFO edge POST /api/feedback 201 18ms
12:04:21 INFO analytics track event=checkout_started
14.2k events / minute retention 30d · structured

More screens

Log Management, screen by screen

/logs ERROR across every service
Log search filtered to ERROR, with the volume chart and the lines that explain each failure
/logs Warnings before the failures
WARN lines: payment-svc reporting 20 of 20 pool connections in use, and slow requests upstream

What it does

What you can do with a log line

/logs?q=
Search text and attributes
Filter on service.name, environment or your own attribute keys, the same way you search message text.
severity
Severity at a glance
Each severity level has its own color and filter. WARN and ERROR are one click apart.
trace_id
Open the trace
Jump from any log line to the span that was running when it was written.
volume histogram
Spot spikes first
A chart above the results, colored by severity, shows an error burst before you read a line.
OTLP
Standard OpenTelemetry
Logs come in over OTLP with your traces and metrics. No extra agent or pipeline.

Keep going

Related features

01

Distributed Tracing

Follow every request across services

→ 02

Error Tracking

Exceptions grouped into issues, linked to the span that threw them

→ 03

Metrics & Dashboards

Browse every metric, build dashboards on them

→ 04

E-Commerce Observability

Trace a failed checkout by its order id

→

Point OTLP at Maple.

One endpoint, one key. Traces, logs, metrics and sessions, linked from the first request.

Start free trial View on GitHub