Ask which Honeycomb triggers are firing, and when the last deploy marker went on.
Connect Honeycomb with a region and a Configuration key for one environment and Memtro reads its datasets and when each last received data, triggers and which are firing, SLOs, boards, and deploy or incident markers. Trigger recipients are never read. It reads on demand and there is no hourly sync. When you ask, and once an administrator has granted the action by name, it can add, change or delete markers, save and run queries, and create boards and SLOs. Markers notify nobody but show on everybody's charts. Deleting a trigger or SLO is permanent and stops its alerts.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Honeycomb tool, reads what it needs, and answers with the source cited.
These tools change something in Honeycomb. 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, choose the kinds you want, and Memtro registers its address with Honeycomb for you. Each event can start a job, with the event as its input. Honeycomb sends a secret with every delivery, and one without it is refused.
Events and webhooksOnce Honeycomb 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.
Honeycomb + MemtroWhich Honeycomb triggers are firing right now?
When did we last deploy the checkout service?
Has any dataset stopped receiving data today?
Add a deploy marker for release 4.12 to the api dataset
Count errors by endpoint on the api dataset over the last 2 hours
At the start of the on-call shift Dan Fletcher asks what is alerting. Memtro lists the two firing triggers, both on the payments dataset with their thresholds, and notes that the payments dataset last received data forty minutes ago.
During an outage Priya Nair asks Memtro to mark when the Northwind integration started failing. Memtro adds an incident marker to the environment's graphs, which notifies nobody but shows on everybody's charts, and sets its end time when she says it is fixed.
The teams that lean on Honeycomb most, a question each of them asks, and what they connect beside it.
A record in Honeycomb 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
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 Honeycomb open Environment settings → API Keys → Configuration and create a Configuration key, not an Ingest key. A key belongs to one environment, so connect each environment separately
Tick Manage Triggers, Manage SLOs, Manage Public Boards and Send Events or Create Markers. Add Manage Queries and Columns to save queries, and Run Queries (Enterprise) to run them. Copy the key: it is shown only while you create it
In Memtro open Connections → Honeycomb, set Region to us if you sign in at ui.honeycomb.io or eu if at ui.eu1.honeycomb.io, paste the Configuration key and connect
Ask which triggers are firing right now
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Honeycomb tools are the same everywhere.
Only when you ask, and only what it has been granted: add a marker (a deploy, incident or note) to an environment's or a dataset's graphs; change a marker's message, type, link or times; delete a marker; save a query specification; run a saved query and read its results; name and describe a saved query; create a board; create an SLO; permanently delete a trigger; permanently delete an SLO. 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.
Region and Configuration key. In Honeycomb open Environment settings → API Keys → Configuration and create a Configuration key, not an Ingest key. A key belongs to one environment, so connect each environment separately.
Yes. Turn events on in the connection's Events tab on the Connections page, choose the kinds you want, and Memtro registers its address with Honeycomb for you. 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
