Which dag failed on our production Deployment overnight, and which task broke it?
Astronomer shows you your Astro workspaces and Deployments with status, Airflow version and executor, and the code deploys to each. On an Airflow 3 Deployment, Memtro also reads dags, dag runs, task instances and import errors. When asked and granted, it can trigger a dag run, pause or unpause a dag, or re-run a dag run or chosen tasks. It can also mark a run success or failed, add a note to a run, hibernate or wake a Deployment, and create a workspace. Dags and runs are read only on Airflow 3 Deployments, and only development Deployments hibernate.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Astronomer tool, reads what it needs, and answers with the source cited.
These tools change something in Astronomer. 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 Astronomer 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.
Astronomer + MemtroWhich dag runs failed on the production Deployment last night?
Which task failed in this morning's billing_export run?
Why is the customer_sync dag missing from the list?
What was deployed to the analytics Deployment this week, and from which commit?
Re-run the failed tasks of last night's warehouse_load run.
Tom Reilly, data platform engineer at BigCo, asked which dag runs had failed overnight on the production Deployment. Memtro listed the failed runs, then read the task instances of each and named the task that had failed with its try number.
Maya Okafor, analytics engineer at Northwind, asked Memtro to re-run the failed tasks of the warehouse_load run. With the action granted, Memtro first listed the tasks that would be cleared, then cleared them on her confirmation so Airflow ran them again.
The teams that lean on Astronomer most, a question each of them asks, and what they connect beside it.
A record in Astronomer 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.
UptimeRobot
Honeycomb
Cronitor
FireHydrant
StatusCake
GlitchTip
GLPI
Langfuse
LibreNMS
NetBox
Snipe-IT
Woodpecker CI
Zabbix
LangSmith
Helicone
GrowthBook
Drata
Intruder
GitGuardian
Secureframe
ilert
JumpCloud
ConfigCat
Split
Aikido Security
Comet Opik
CrowdStrike Falcon
Detectify
Domotz
LambdaTest
LangWatch
LlamaCloud
Logz.io
Lunary
NinjaOne
Northflank
Portkey
PromptLayer
PRTG Network Monitor
Raygun
Retell AI
Runpod
Shodan
Spike.sh
Squadcast
Tenable
UpGuard
Uptime.com
Vanta
Zenduty
Cortex
WorkOS
Kandji
Automox
Huntress
SimpleMDM
Healthchecks.io
Rapid7 InsightVM
ZenhubIn Astro, open Settings → Access Management → API Tokens and create an Organization API Token. Workspace Member reads, Workspace Operator or Deployment Operator triggers and re-runs, and Organization Owner creates workspaces.
Open Connections → Astronomer in Memtro and paste the API token and the Organization ID from your organization settings.
An administrator grants actions such as trigger a dag run or hibernate a Deployment by name to the teams that may use them.
Ask which dag runs failed on the production Deployment last night.
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Astronomer tools are the same everywhere.
Only when you ask, and only what it has been granted: trigger a dag run on a Deployment; pause or unpause a dag; re-run (clear) a dag run; re-run (clear) chosen task instances of a dag run; mark a dag run as success, failed or queued; add or replace the note on a dag run; hibernate or wake a development Deployment; end a Deployment's hibernation override; create a workspace. 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 token and organization ID. In Astro, open Settings → Access Management → API Tokens and create an Organization API Token. Workspace Member reads, Workspace Operator or Deployment Operator triggers and re-runs, and Organization Owner creates workspaces.
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
