Observability

Three questions get asked once Auron is in real use: is it being used, is it producing anything worthwhile, and what happened in that particular case. Each has a place to look.

Is it being used

The usage half of Analytics reports activity across the organization: meetings and chats and how they ended, agent minutes and user minutes as totals and trends, daily and monthly active users, who has gone dormant, activity per agent, and how many entities are active.

The entity numbers are the ones worth watching early. Records being created faster than anyone organizes them shows up here as untagged entities long before it shows up as a complaint.

Is it producing anything

The signal half of the same screen reports what is being detected: how volume is trending, how confident detections are, which agents contribute most, and how signals group by entity.

Read confidence alongside volume. A rising count of low-confidence detections usually means a signal definition needs tightening rather than that more is happening.

What happened in that case

For a session, the transcript is the record, and reasoning and tool lookups are available as a trace rather than being hidden.

For an automation, every run is recorded and can be opened stage by stage, showing what went in, what came out and where it failed. See Automations.

For a webhook, deliveries and failures are visible in the same place they are configured.

What it cost

Credit consumption is reported as a history, broken down by what caused it, and by year. The breakdown by source is the useful one: it tells you whether spend is going on voice sessions, chats, reports or signal processing, which is what you would act on. See Usage and plan.

Asking for something that is not there

Analytics has a request option for a chart or metric you keep wanting and cannot build. For a one-off question, Ask Auron will usually produce the answer, and often the chart, directly.