Cost control: a monthly token allowance for each modelSee how it works
memtro
Start for free

SigNoz + Memtro

Which SigNoz alerts are firing, and how many errors did checkout log?

SigNoz answers what is wrong right now, whether you use Cloud or self-host. You see alert rules and their state, alerts firing now, a rule's state history, dashboards, metric names, maintenance windows, and counts, rates and percentiles over logs, traces and metrics grouped by service. When asked and granted, Memtro can enable, disable, clone or delete alert rules, create, change or delete maintenance windows that mute alerts, and clone, lock or delete dashboards. SigNoz can tell Memtro when an alert fires or resolves, and a job can start on it. Queries return aggregates, never raw log lines or spans.

Connect SigNozStart for freeReference
In Memtro

What you can do with SigNoz in Memtro

Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right SigNoz tool, reads what it needs, and answers with the source cited.

What it does

  1. 01See alert rules by state and severity, and the alerts firing now with summary and start time.
  2. 02Follow a rule's state changes over up to 31 days, with time, state and value.
  3. 03Count, rate or take percentiles over logs, traces and metrics, grouped by service or other fields.
  4. 04List dashboards, metric names and maintenance windows with their schedule and the rules they cover.
  5. 05When asked and granted, enable, disable, clone or delete alert rules, or set a maintenance window that stops them notifying anyone.
  6. 06With events on, an alert that starts firing or one that resolves in SigNoz can start a job.

Acts when asked

When you ask it to

These tools change something in SigNoz. 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.

  1. 01Enable or disable an alert rule
  2. 02Clone an alert rule
  3. 03Delete an alert rule
  4. 04Create a planned maintenance window that mutes named alert rules
  5. 05Change a planned maintenance window
  6. 06Delete a planned maintenance window
  7. 07Clone a dashboard
  8. 08Lock or unlock a dashboard
  9. 09Delete a dashboard

Events

When it happens

Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in SigNoz, choosing the same kinds; the tab shows SigNoz's own steps. Each event can start a job, with the event as its input. SigNoz sends a secret with every delivery, and one without it is refused.

Events and webhooks
  • 01An alert started firing
  • 02An alert resolved
In practice

Ask it like you would a colleague

Once SigNoz 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.

SigNoz + Memtro

  • Which SigNoz alerts are firing right now?

  • How many errors did checkout log in the last hour?

  • What is the p99 latency of the payments service today?

  • When did the High CPU rule last fire and resolve?

  • Which maintenance windows are coming up this week?

01

Errors after a deploy

Tom Reilly, platform engineer at BigCo, asked how many errors checkout logged in the last hour. Memtro ran a count over logs filtered to the checkout service and error severity, and listed the alerts firing alongside it.

02

Firing alert triage job

At Acme Ltd, a job starts when SigNoz sends an alert that started firing. Memtro reads the rule, its state history for the last day and an error count for the service named in its labels. It then gives Sarah Chen, the on-call engineer, a summary.

Teams

Where it fits

The teams that lean on SigNoz most, a question each of them asks, and what they connect beside it.

Better together

Works with

A record in SigNoz 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.

Also in Engineering and operations

Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.

Setup

How to connect

Connect withSigNoz host and Service account API key
  1. 1

    In SigNoz, an administrator goes to Settings, then Service Accounts, creates one with the signoz-viewer or signoz-editor role, and adds a key on its Keys tab.

  2. 2

    In Memtro, open Connections → SigNoz and enter the SigNoz host, host name only, and the Service account API key. Fill in Port only for a self-hosted SigNoz not on 443.

  3. 3

    An administrator grants the actions by name, such as Delete alert rule or Create maintenance window, to the teams that may use them. The key's role also caps what can change.

  4. 4

    Ask which SigNoz alerts are firing. Events are turned on from the connection's Events tab, and the address is then added as a webhook notification channel in SigNoz.

Also works from

Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The SigNoz tools are the same everywhere.

Set it up as an MCP serverClients and agents
FAQ

Questions

Can Memtro change anything in SigNoz?+

Only when you ask, and only what it has been granted: enable or disable an alert rule; clone an alert rule; delete an alert rule; create a planned maintenance window that mutes named alert rules; change a planned maintenance window; delete a planned maintenance window; clone a dashboard; lock or unlock a dashboard; delete a dashboard. 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.

Who can use a SigNoz connection?+

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.

Does Memtro store my SigNoz data?+

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.

How do I connect SigNoz?+

SigNoz host and Service account API key. In SigNoz, an administrator goes to Settings, then Service Accounts, creates one with the signoz-viewer or signoz-editor role, and adds a key on its Keys tab.

Can SigNoz start a job?+

Yes. Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in SigNoz, choosing the same kinds; the tab shows SigNoz'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.

Connect SigNoz in a few minutes

Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.

Start for freePricing

Where agents remember your company

Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.

Start for freeGetting started

7-day free trial · card on file, nothing charged until it ends · cancel any time