Ask what caused last night's Dynatrace problem, which services it hit, and how SLOs stand.
Connect Dynatrace with your environment host and a classic access token and Memtro reads problems with their status, severity, impact, root-cause entity, affected entities, evidence and comments, along with events such as deployments and configuration changes, monitored hosts and services, metric queries and SLOs with their error budget. It reads on demand and there is no hourly sync. When asked, and once an administrator has granted the action by name, it can add, edit or permanently delete problem comments, close a problem, which cannot be reopened, and record deployment or annotation events, which consume billable Davis Data Units.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Dynatrace tool, reads what it needs, and answers with the source cited.
These tools change something in Dynatrace. 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, then add the address it shows as a webhook in Dynatrace, choosing the same kinds; the tab shows Dynatrace's own steps. Each event can start a job, with the event as its input. Dynatrace sends a secret with every delivery, and one without it is refused.
Events and webhooksOnce Dynatrace 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.
What caused the alert on the checkout service last night?
Which Dynatrace problems are still open, and what is the root cause of each?
Was there a deployment on the payments service before the error rate went up?
Which SLOs are in warning or failing, and how much error budget is left?
Record a deployment event on the checkout service for release 4.2
The on-call engineer asks what woke the pager at 2am. Memtro finds a problem on the Acme checkout service, names the root-cause entity, shows a deployment event ten minutes before it opened, and lists the two comments already on it.
Once the rollback has held for an hour, Dan Fletcher asks Memtro to close the Northwind checkout problem with a note that release 4.2 was rolled back. Memtro closes the problem with that closing comment, which everyone who can see the problem in Dynatrace now reads.
The teams that lean on Dynatrace most, a question each of them asks, and what they connect beside it.
A record in Dynatrace 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
Astronomer
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 Dynatrace open Access Tokens → Generate new token and select problems.read, events.read, entities.read, metrics.read and slo.read, plus problems.write only if Memtro should comment on or close problems and events.ingest only if it should record events
Use a classic access token starting dt0c01., not a platform token, and copy it now: it is shown once
In Memtro open Connections → Dynatrace, paste the API token and the Environment host from your browser's address bar, such as abc12345.live.dynatrace.com, with no https://, path or port. On Managed type your cluster's host and the Environment ID after /e/
Ask what caused the alert on the checkout service last night
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Dynatrace tools are the same everywhere.
Only when you ask, and only what it has been granted: add a comment to a problem; edit a comment on a problem; delete a comment from a problem (permanent); close a problem with a closing comment; record an annotation, deployment, configuration or info event on entities (consumes Davis Data Units). 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.
Environment host and API token. In Dynatrace open Access Tokens → Generate new token and select problems.read, events.read, entities.read, metrics.read and slo.read, plus problems.write only if Memtro should comment on or close problems and events.ingest only if it should record events.
Yes. Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in Dynatrace, choosing the same kinds; the tab shows Dynatrace's own steps. 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
