Capability
Observability
Every run leaves a trace: inputs, tool calls, model versions, cost, approvals and outcome, queryable long after the process finished.
Observability
Observability in ÆTERION BRAIAN records what actually happened. Each run produces a structured trace of steps, tool calls, data touched, model and prompt versions, cost, latency, human approvals and the final outcome. Traces are retained under your policy and can be searched, exported and attached to an audit request without reconstructing anything from application logs.
What does a trace contain?
- The process and version that ran, and who or what triggered it.
- Each step: inputs, outputs, duration, cost and the policy that authorised it.
- Every external call: system, operation, record identifiers, success or failure.
- Human interventions: who approved, changed or rejected, and when.
- The final outcome and any downstream effect the run produced.
Operations and finance in one view
The same data answers two different questions: whether the process is healthy, and what it costs. Cost is attributed per process, per team and per model, so budget conversations use measured numbers.
How long is data retained, and how do you export it?
- Retention
- Trace retention is a policy setting, aligned to your records-management rules.
- Export
- Traces export to your SIEM or data warehouse for long-term analysis.
- Access
- Who may read traces, and which fields they see, is governed by the control plane.
FAQ
Are traces suitable as audit evidence?
They are designed for it: append-only, attributable and complete for the run, including the policy version in force at the time.
Can we alert on this data?
Yes. Thresholds on failure rate, override rate, latency or cost raise alerts to your existing on-call channels.
See what your automation actually does
We show a real trace end to end, from trigger to recorded outcome.