Skip to content

Join the waitlist

Be first in line when Dispra Cloud opens up. We’ll email you when your spot is ready.

Logs

Logs that explain what happened

Every request is a tree of steps you can open. Select the lines that matter and ask why.

Join the waitlist

Be first in line when Dispra Cloud opens up. We’ll email you when your spot is ready.

Traces, not walls of text

A request opens into auth, database, cache and outbound calls, each with its own time.

Select and ask

Drag across lines, then ask AI. Answers point back to the exact lines they used.

Live, filtered, searchable

Filter by service and level, search with status:500, or follow new lines as they arrive.

How logs work on Dispra Cloud

Every service writes to standard output, and Dispra Cloud collects it. You don’t install an agent or change your code. Lines from all your services and replicas land in one place, in order, within a second or two.

Lines that belong to the same request share a trace. Instead of a long list, you see one row per request that opens into the steps inside it, each with how long it took. Slow and failing steps stand out on their own.

A checkout request, opened into the nine steps it took. The amber line is the retry that made it slow.

What each line carries

Dispra adds the fields below to every line. You can filter and search on any of them.

FieldExampleWhat it’s for
time13:52:40.977When the line was written, to the millisecond.
serviceapiWhich service in the project wrote it.
levelWARNInfo, debug, warn or error. Filter by it.
eventhttp.retryA short name for what happened, so lines group well.
trace9e1f…c2Ties every line from one request together.
replicaapi-2 · MumbaiWhich copy of the service, in which region.

Asking about a selection

Drag across the lines you care about, or shift-click to add more. Then ask a question in the side panel. The answer only uses what you selected, and every claim links back to the line it came from.

AI chat
Aarav · just now4 log lines
Why did this checkout take 1.4 s?

Most of the 1.4 s was the Stripe call retrying.

The first attempt timed out after 800 ms+44 mshttp.retry, the second succeeded in 512 ms+846 mshttp.retry. Everything else in the request took under 60 ms.

Lowering the Stripe client timeout to 300 ms and retrying sooner would cut this to roughly 0.9 s.

4 lines · checkout trace
Ask about the selection…
Drag across rows or shift-click to add context
Ask about the lines you selected. The answer links back to them.

Search syntax

Type into the search box to narrow the list. Combine terms to narrow it further.

SearchFinds
status:500Requests that returned a 500
service:api level:errorErrors from the api service
trace:9e1fEvery line from one request
"payment_intents"Lines containing that text
since:15mOnly the last 15 minutes

How long logs are kept

PlanKept forLive tail
Hobby—Yes
Pro—Yes
Team—Yes, plus export

Need logs for longer? Send them to your own storage with a log drain, set up from the project’s settings.

Your next push could be live.

Join the waitlist

Be first in line when Dispra Cloud opens up. We’ll email you when your spot is ready.