The AI SRE agent for modern teams
Aro turns SigNoz alerts into shared investigations — with memory, Slack collaboration, and approved actions across Linear, GitHub, and Notion.
Incident notebook
checkout · Payments · live from SigNoz
7 signals
cart_tax_v2
Ready for Slack
Working theory
Sync tax path in `cart_tax_v2` is blocking checkout. Flip the gate, watch p99 for 10 minutes, open Linear if it holds.
01 · Incident begins
An alert becomes a shared investigation
When SigNoz fires, Aro correlates related signals into one incident — with severity, owner hints, and a notebook ready for the team.
Signal intake
SigNoz → Aro
Source: SigNoz alert · threshold breached · checkout p95
Checkout p95 latency spike after deploy
checkout · Payments
SigNoz alert grouped 7 related signals on checkout. p99 climbed to 1.2s after cart_tax_v2 rolled out.
02 · Investigate
Ask Aro — with real tool calls, not a black box
Click a probe. Aro walks SigNoz, memory, runbooks, and code context the same way it does in the product notebook.
Ask Aro
Incident chat · checkout
Pick a question to start investigating
Each chip simulates tool calling across dashboard, memory, GitHub, and Notion.
Context Aro can pull
SigNoz dashboards
Metrics, logs, traces, and service maps for the alert window.
Workspace memory
Prior decisions, learnings, and owner notes from past incidents.
Notion runbooks
Cached playbooks so the team follows the same steps.
GitHub / code context
Recent PRs and commits that line up with the deploy marker.
03 · Act
Take the next step with human approval
Create a Linear issue, update Slack, tag an owner, inspect the PR, or draft a fix — Aro proposes, your team confirms.
Suggested actions
Stage 4 · nothing runs until you click
Human gate
Aro will not open tickets, post Slack, or touch code until you trigger an action below.
04 · Slack collaboration
Same incident context, in the channel your team already uses
Aro posts the alert, answers @mentions with memory and notebook context, and keeps Slack tied to the same investigation as the dashboard.
#incidents
Connected to incident · demo-checkout-p95
05 · Memory
Every investigation makes the next one faster
Replies, decisions, evidence, and runbooks persist in workspace memory. Dump docs and notes anytime — Aro keeps learning with your team.
Workspace memory
Library · graph · ingest
06 · Resolve
Close the loop — incident, Slack, task, and memory
When the gate is flipped and p99 recovers, Aro marks the incident resolved, updates the channel, and keeps the learning for next time.
Final state
Still investigating
Checkout p95 latency spike after deploy
checkout · Payments
SigNoz alert grouped 7 related signals on checkout. p99 climbed to 1.2s after cart_tax_v2 rolled out.
Slack
Thread open · awaiting recovery
Linear
Issue draft ready
Memory
Evidence collecting…