Overnight outage at BigCo
Priya Sharma, network engineer at BigCo, asked what had gone down overnight. Memtro read the PRTG log and listed the sensors that changed to Down, with their messages.
Which sensors are down right now, and what changed overnight?
PRTG Network Monitor shows you sensors that are down, warning or unusual, with their message and last value. It reads devices with sensor counts per state, the log of state changes, tickets, and one sensor's channels and historic data. When asked and granted, it can acknowledge an alarm, pause or resume an object, scan a sensor now or run an auto-discovery. It can also rename, tag, prioritise, duplicate or delete an object, send a test notification, and add an object to a report. Device host names and IP addresses are never returned.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right PRTG Network Monitor tool, reads what it needs, and answers with the source cited.
These tools change something in PRTG Network Monitor. 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 PRTG Network Monitor 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 sensors are down right now?
Which devices have sensors in warning?
What was the ping time on the core switch yesterday?
What changed state in the last hour?
Which tickets are still open?
Priya Sharma, network engineer at BigCo, asked what had gone down overnight. Memtro read the PRTG log and listed the sensors that changed to Down, with their messages.
Tom Reilly at Northwind asked Memtro to acknowledge the Down alarm on the backup link while the carrier fixed it. With the action granted, Memtro acknowledged it with his message, so its notifications stopped repeating.
The teams that lean on PRTG Network Monitor most, a question each of them asks, and what they connect beside it.
A record in PRTG Network Monitor 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 PRTG open Setup, then Account Settings, then API Keys, and add a key of token type Scripting. Pick the access level the actions need. It is shown once.
In Memtro open Connections → PRTG Network Monitor, fill in Server with the host name only, and paste the API key.
Set Port only if PRTG is not on 443. An administrator grants the alarm, pause and delete actions by name to the teams that may use them.
Ask: which sensors are down right now?
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The PRTG Network Monitor tools are the same everywhere.
Only when you ask, and only what it has been granted: acknowledge a Down alarm on a sensor; pause monitoring of an object (indefinitely or for some minutes); resume monitoring of a paused object; scan a sensor now; run an auto-discovery on a group or device (may add sensors); rename an object; set an object's priority; set an object's tags; duplicate a group, device or sensor; delete an object and everything under it; send a test of a notification template to its recipients; add an object to a report. 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.
Server and API key. In PRTG open Setup, then Account Settings, then API Keys, and add a key of token type Scripting. Pick the access level the actions need. It is shown once.
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