Ten fewer steps
Alerts, traces, logs, sessions and changes, time-aligned.
When the alert fires, context is scattered
Metrics in one system, logs in another, traces in a third, change records in a chat thread. The first step is finding an entry point; analysis comes after.
Diting aligns them in time. Start at the anomaly and follow the call chain down.
Alert, trace, session
See the anomaly
Find the request
See the scene
Match the change
Incident timelineDiting
01Slow query
SELECT … WHERE order_id = ?02Owning request
03User session
The cause comes from traces and sessions
From anomaly to the click, every step is on record. Share one link for the postmortem.
- Alert to trace
- Trace to logs
- Logs to session
- Session to replay
Fits
- Mixed microservice and monolith estates where blast radius is unclear
- Teams that need fast postmortems
Doesn't fit
- Estates with no capture and no permission to add it
Bring your system in
Tell us what you run: OS, kernel, public network or not, virtual machines or clusters. We will map the path in.