Skip to main content
Every alert Ordyn surfaces, and every question you ask it, produces an investigation. An investigation is a structured report, not a chat transcript.

​
What it contains

  • Root cause. What went wrong and why. If Ordyn is weighing more than one explanation, it says so and ranks them.
  • Impact. Who and what is affected, and how badly.
  • Timeline. The events leading up to the problem, including recent deploys and pull requests.
  • Evidence. Every claim links to the log line, metric, trace, or code it came from. Hover a citation to see the query snapshot, or click through to run it yourself in the app.
  • Confidence. A score from 1 to 5. A 5 means conclusive, verified evidence. A 4 means strong evidence with few alternatives. Lower scores mean you should look before you act.
  • Suggested fix. What to change, and a button to have Ordyn or your coding agent make the change. See Fix with Ordyn.
Ordyn does not claim certainty it does not have. The confidence score and the evidence links are there so you can check the work.

​
Follow up

Reply in the Slack thread, or continue in the app, and Ordyn picks up with the full investigation in context. You can ask it to explore a different hypothesis, pull more data, or explain a step.

​
The Investigations page

Investigations in the app lists every investigation with its status and outcome, plus two running metrics: mean time to root cause and engineering hours recovered. Open any investigation to see the full report and the path Ordyn took to get there. You can cancel an investigation that is still running from its page.