Morning handover
Tom Reilly, SRE lead at BigCo, asked what fired overnight. Memtro listed the alert groups with state, alert count and who acknowledged or resolved each, and named who is on call next.
Who is on call for the platform team in Grafana OnCall right now?
Grafana OnCall connects Memtro to on-call and alerts in Grafana Cloud IRM. It reads alert groups by state, integration, team and label with resolution notes, and who is on call now, next or before. It also reads integrations, users, teams and shift swaps. When asked and granted, it can acknowledge, resolve, silence, escalate, attach, label or delete alert groups, add resolution notes, page people, start or stop maintenance, and request or take shift swaps. With events on, OnCall tells Memtro when an alert group is created or resolved, and a job can start on it. Alert payloads are never returned.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Grafana OnCall tool, reads what it needs, and answers with the source cited.
These tools change something in Grafana OnCall. The model is told to use them only when you ask for exactly that, and an administrator grants each one by name to the teams that may use it; a personal connection acts only after its owner allows it.
Turn events on in the connection's Events tab on the Connections page, choose the kinds you want, and Memtro registers its address with Grafana OnCall for you. Each event can start a job, with the event as its input. Grafana OnCall sends a secret with every delivery, and one without it is refused.
Events and webhooksOnce Grafana OnCall is connected, these are the kinds of things people ask. Plain questions, no syntax. If the answer lives partly in another system you have connected, Memtro looks there too.
Who is on call for the platform team right now?
Which alert groups have not been acknowledged in the last day?
Which integrations are in maintenance?
What resolution notes were left on alert group 1423?
Which shift swap requests are still open this week?
Tom Reilly, SRE lead at BigCo, asked what fired overnight. Memtro listed the alert groups with state, alert count and who acknowledged or resolved each, and named who is on call next.
At Acme Ltd, a job starts when an alert group is resolved in Grafana OnCall. It reads the alert group and who was on call and, as granted, adds a resolution note naming the responder. Priya Sharma's platform team sees it on the alert group's timeline.
The teams that lean on Grafana OnCall most, a question each of them asks, and what they connect beside it.
A record in Grafana OnCall is rarely the whole story. Connect the systems that hold the rest and Memtro checks them together, then remembers what it learned so the next question starts further along.
Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.
In Grafana Cloud, open Administration, Users and access, Service accounts. Add a service account with the IRM permissions Memtro needs, then add a token and copy it. The OnCall API URL is under IRM, Settings, Admin & API.
In Memtro, open Connections → Grafana OnCall and enter the OnCall API URL, the Service account token and your Grafana stack URL, which the token needs.
An administrator grants the actions by name, such as paging, to the teams that may use them. Events are turned on from the connection's Events tab, which needs the outgoing-webhooks:write permission.
Ask who is on call for the platform team.
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Grafana OnCall tools are the same everywhere.
Only when you ask, and only what it has been granted: acknowledge an alert group (stops its escalation); unacknowledge an alert group (restarts its escalation); resolve an alert group; reopen a resolved alert group; silence an alert group for a time or for good; unsilence an alert group; advance an alert group's escalation to the next step (notifies people); attach an alert group to another; add an existing label to an alert group; delete or wipe an alert group (permanent); add a resolution note to an alert group; page a team or people (notifies them); start maintenance on an integration; stop maintenance on an integration; request a shift swap; take a shift swap request (changes who is on call). Every other tool reads, searches or lists. The Connections page labels the tools that act, an administrator grants each one by name to the teams that may use it, and a personal connection acts only after its owner allows it.
A personal connection serves only your own requests. A shared connection serves the organisation: everyone, or only the teams an admin chooses. Admins can always add shared connections; other members need the permission.
Credentials are encrypted at rest. Tool results are cached briefly so agent loops do not repeat identical calls, and the facts the model extracts are saved to your organisation's memory with provenance (system, record and link) so they can be checked and superseded.
OnCall API URL and service account token. In Grafana Cloud, open Administration, Users and access, Service accounts. Add a service account with the IRM permissions Memtro needs, then add a token and copy it. The OnCall API URL is under IRM, Settings, Admin & API.
Yes. Turn events on in the connection's Events tab on the Connections page, choose the kinds you want, and Memtro registers its address with Grafana OnCall for you. A job set to start "When an event arrives" then runs once for each matching event, with the event as its input. The run treats the event as outside data, never as instructions, and anything the run remembers is kept as unverified.
Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.
Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.
7-day free trial · card on file, nothing charged until it ends · cancel any time