Operations | Monitoring | ITSM | DevOps | Cloud

Checkout starts failing because the cart service keeps dying. The real cause is a recent pull request that let memory grow with every add to cart.

You get an answer from the agent and no way to check how it got there. The route it took is recorded, and so is the reason it gave for taking it. AURA emits OpenTelemetry spans, and the Docker quickstart wires them straight into Phoenix. Four services come up together: AURA Web Server as the persistent agent harness, LibreChat as a browser interface for chatting with the agent, Phoenix to receive the spans, and MongoDB to store stateful data for LibreChat. The Compose file arrives pre-configured to point AURA at Phoenix and to enable content recording for the local demo.

The same agent that reads a Kubernetes cluster reads a Windows machine. One MCP server, one config entry, and the questions are the ones you already ask.

Building an agent and not sure how to approach something? Bring it. AURA office hours are recurring working sessions with the people who build it. The team has been talking to people trying out AURA and hearing the same good questions come up more than once. Office hours are the answer to that: a standing slot on a schedule, rather than one conversation at a time. The format is deliberately loose. Nobody is arriving with thirty slides to spend an hour talking at you. The session goes wherever the questions go.

A big tool result does not have to be a big context cost. AURA moves it to disk and hands the model a pointer plus the tools to navigate what is there. A large MCP tool result can consume or overflow an agent's context window, and on a third-party server you do not control how much comes back. Scratchpad breaks the link between how big a tool result is and how much context it costs: the full output goes to disk, and only the slice the model asks for ever enters the window. Errors always pass through inline, so the model can react to them.

The model, the serving layer, and the agent asking questions all sit on local hardware. The first thing it debugs is the AI stack it is running on. No external inference provider in the path.

Give one agent every tool and every incident is a question of trust. This one hands each job to a worker that can only reach what that job needs. One AURA configuration defines a coordinator and three specialist workers. Qdrant stores the runbooks, Prometheus measures workload health, and Kubernetes provides inspection and remediation, and each of the three is wired to one worker.

AI is changing every stage of the reliability-engineering career path. Applications are harder to distinguish, traditional coding tests reveal less, junior opportunities are shrinking, and the knowledge expected of an SRE keeps expanding.

An on-call question returns the threshold and the escalation owner from your own runbooks, and the answer comes back without a call to anyone outside. AURA runs against Bedrock as its model provider, using Claude Sonnet 5 served by AWS in the same region. Authentication is the normal AWS credential chain: a profile on a laptop, an IAM role in EKS.