The pulse of production, on one screen.

What does the Console show?

Four figures sit across the top of the Console. Each one answers a question an engineering leader asks about production.

• Open incidents: the incidents still open, triaged from every open alert.
• MTTR reduction: the time NeuBird investigations have taken off resolving incidents.
• Cost savings: the value of that time, based on the number of alerts NeuBird investigated.
• Agent confidence: how confident the agent is in its root cause findings.

How does the service map work?

Below the figures, the service map draws your environment as it runs: services in AWS, Azure and on-premises data centers, and the dependencies between them. Hybrid estates are hard to hold in anyone's head, so the map holds it for you.

Engineers and the agents investigating read the same map in real time. When an agent traces a failure, it follows the dependencies you can see on screen.

What happens when an incident hits?

The services an incident affects turn red on the map. Hovering over one shows what is wrong with it, such as a database whose connection pool is exhausted or an API whose latency has climbed, and which services sit upstream and downstream of it.

From there, one prompt asks the agent to investigate the entire issue chain rather than a single alert. The investigation opens in Investigations, with its root cause, evidence and fix.

Where does the data come from?

The Console reads from the tools you have connected in Connections. NeuBird queries telemetry where it already lives, with zero telemetry storage: raw logs, metrics and traces are never copied into another store.