Unacknowledged P1s at handover
Tom Reilly, an on-call engineer at BigCo, asked which P1 cases were still unacknowledged at shift handover. Memtro listed them with their impacted services, labels and how long each had been open.
Which P1 cases in Coralogix are still unacknowledged?
Coralogix watches your systems and raises cases and incidents. Memtro reads cases with status, priority, category, impacted services, labels and their timeline, incidents with severity, state and status, and SLOs with their targets. When asked and granted, it can comment on a case, acknowledge, assign, reprioritise, rename, resolve or close it, and acknowledge, assign, resolve or close incidents by id. The API key is region-bound, and each case permission is added to it one by one. Comment text and who did what on a timeline are never returned.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Coralogix tool, reads what it needs, and answers with the source cited.
These tools change something in Coralogix. 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.
Once Coralogix 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.
Which P1 cases are still unacknowledged?
What happened on CASE-123 since it opened?
Which incidents are triggered for the payments application?
What is the target on our checkout latency SLO?
Acknowledge CASE-123 and assign it to me.
Tom Reilly, an on-call engineer at BigCo, asked which P1 cases were still unacknowledged at shift handover. Memtro listed them with their impacted services, labels and how long each had been open.
Maya Okafor, an SRE at Northwind, asked Memtro to acknowledge CASE-412 and add a comment that a rollback was under way. Memtro did both, and the comment appeared on the case's timeline for everyone who could see it.
The teams that lean on Coralogix most, a question each of them asks, and what they connect beside it.
A record in Coralogix 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 Coralogix, open Settings → Users and Teams → API Keys and select + Key. Add case:Read and incidents:read, plus only the case and incident permissions for actions you want, then copy the key.
In Memtro, open Connections → Coralogix, paste the API key and choose the Region from the domain you sign in on.
With a personal key, comments and assignments are made as you. An administrator grants the case and incident actions by name to the teams that may use them.
Ask which P1 cases are still unacknowledged.
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Coralogix tools are the same everywhere.
Only when you ask, and only what it has been granted: comment on a case; acknowledge or unacknowledge a case; assign or unassign a case; set or clear a case's priority override; rename a case or change its resolution reason; resolve a case; close a case; acknowledge incidents by id; assign incidents by id to a user; resolve incidents by id; close incidents by id. 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.
API key and region. In Coralogix, open Settings → Users and Teams → API Keys and select + Key. Add case:Read and incidents:read, plus only the case and incident permissions for actions you want, then copy the key.
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