Logs, metrics, and traces in one place.

Find production issues and investigate them with RSL, our query language.

Any serviceLast 1 hour

Duration · last hour · 797 traces

TimeStatusOperationDurationSpansServicesErrors

14:02:11.482OKcheckoutGET /cart38 ms62—

14:02:10.907ErrorcheckoutPOST /charge412 ms1443

14:02:10.311OKinventoryGET /stock/:sku21 ms31—

14:02:09.854OKcheckoutGET /orders/:id64 ms83—

14:02:09.120OKpaymentsPOST /refund133 ms93—

14:02:08.733OKcheckoutPOST /charge188 ms114—

14:02:08.045OKledgerPOST /append47 ms51—

14:02:07.598OKcheckoutGET /cart41 ms62—

14:02:06.990OKcheckoutPOST /charge205 ms114—

14:02:06.211OKinventoryPOST /reserve29 ms41—

14:02:05.876OKcheckoutGET /health2 ms11—

For teams running services in production

When something breaks, logs, traces, metrics and infrastructure live in different tools, and the clock runs while you line them up.

How ReasonOS fixes it

01

Send logs, metrics and traces over OTLP with a project ingest token.

02

Errors, services, a service map and infrastructure views link to the traces and logs behind them.

03

Monitors are scheduled RSL queries with threshold or anomaly conditions. Alerts can go to Slack.

Your team and your agents join with a link.