How many checkout errors were logged in the last hour?
Mezmo, formerly LogDNA, connects Memtro to your log analysis. It searches log lines over a time window by query, host, app and level. It also reads saved views and their alert triggers, preset alerts, boards, storage usage, exclusion rules and whether logs are being ingested. When asked and granted, it can create or delete views and email alerts, create, switch or delete exclusion rules, resume ingestion, and invite or remove members. Mezmo can also tell Memtro when a view's alert fires, and a job can start on it. You attach that webhook alert in Mezmo yourself.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Mezmo tool, reads what it needs, and answers with the source cited.
These tools change something in Mezmo. 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 Mezmo, choosing the same kinds; the tab shows Mezmo's own steps. Each event can start a job, with the event as its input. Mezmo sends a secret with every delivery, and one without it is refused.
Events and webhooksOnce Mezmo 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.
How many checkout errors were logged in the last hour?
Show the latest error lines from the payments app.
Which apps used the most log storage last week?
Are we ingesting logs right now?
Switch off the health check exclusion rule.
Dan Fletcher, on-call engineer at Northwind, asked how many checkout errors were logged in the last hour. Memtro searched the checkout app at error level and showed the latest lines. He saw they came from one host and restarted it.
When the payments view's alert fired at Acme Ltd, Mezmo told Memtro and a job started. It searched the matching log lines and summarised the hosts and apps involved for Sarah Chen, the platform lead. Nothing in Mezmo changed.
The teams that lean on Mezmo most, a question each of them asks, and what they connect beside it.
A record in Mezmo 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 Mezmo, open Settings → Organization → API Keys and create a service account or personal key with read permissions, and write permissions for the actions you will grant. Not the ingestion key.
In Memtro, open Connections → Mezmo and paste the Access key.
An administrator grants the actions by name, such as Remove a member from the organization, to the teams that may use them. Events are turned on from the connection's Events tab, and a Webhook alert is then attached to the view in Mezmo.
Ask "How many checkout errors were logged in the last hour?"
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Mezmo tools are the same everywhere.
Only when you ask, and only what it has been granted: create a saved view, optionally with an email alert; delete a saved view and its alerts; create a preset email alert; delete a preset alert; create an exclusion rule that stops matching lines being stored; switch an exclusion rule on or off, or change it; delete an exclusion rule; resume log ingestion after a suspension; invite a member to the organization with a role; remove a member from the organization. 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.
Access key. In Mezmo, open Settings → Organization → API Keys and create a service account or personal key with read permissions, and write permissions for the actions you will grant. Not the ingestion key.
Yes. Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in Mezmo, choosing the same kinds; the tab shows Mezmo'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
