Monday incident review
Priya Sharma, data platform lead at Acme Ltd, asked which incidents opened last week and who owned them. Memtro listed each incident with its severity, tables, owner and Jira ticket, and flagged the two with no owner.
Which data incidents opened this week, and who owns them?
Monte Carlo watches your tables, and Memtro lets you ask about it in plain words. It reads alerts and incidents on freshness, volume, schema, custom SQL, metric and dbt failures, by status, severity, owner and table. It reads monitors with their last and next run, searches the catalog for tables and other assets, and lists connected warehouses. When asked and granted, it can set an alert's status, declare or clear an incident, assign an owner and comment. It can also pause, run, snooze or delete monitors. Alert windows reach back at most 65 days.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Monte Carlo tool, reads what it needs, and answers with the source cited.
These tools change something in Monte Carlo. 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 Monte Carlo 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 data incidents opened this week, and who owns them?
Which freshness alerts are still unacknowledged?
Which monitors are snoozed or in error right now?
Is the orders table monitored, and in which warehouse?
Mark the alert on the payments table as acknowledged.
Priya Sharma, data platform lead at Acme Ltd, asked which incidents opened last week and who owned them. Memtro listed each incident with its severity, tables, owner and Jira ticket, and flagged the two with no owner.
Tom Reilly, analytics engineer at BigCo, asked Memtro to snooze a volume monitor during a planned backfill. Memtro snoozed it for 120 minutes and recorded his reason as a monitor comment the team could see.
The teams that lean on Monte Carlo most, a question each of them asks, and what they connect beside it.
A record in Monte Carlo 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 Monte Carlo, go to Settings, then API, then Add. Choose a personal or account key and an expiry. Account keys need the Account Owner permission.
In Memtro, open Connections → Monte Carlo and paste the Key ID and the Secret. The secret is shown only once.
An administrator grants the alert and monitor actions by name to the teams that may use them. If network access control is on, allow Memtro's address.
Ask which data incidents opened this week and who owns them.
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Monte Carlo tools are the same everywhere.
Only when you ask, and only what it has been granted: set an alert's status (acknowledged, fixed, expected and so on) or rename it; declare an alert an incident with a severity, or clear it; assign an alert to an owner; comment on an alert, or edit a comment; delete an alert comment; pause or resume a monitor; run a monitor now; snooze a monitor for a number of minutes; unsnooze a monitor; delete a monitor. 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.
Key ID and Secret. In Monte Carlo, go to Settings, then API, then Add. Choose a personal or account key and an expiry. Account keys need the Account Owner permission.
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