Sumo Logic + Memtro

Ask Sumo Logic what errors a service logged this morning, and which monitors are triggered.

Connect Sumo Logic with an access ID, access key and your deployment and Memtro searches logs with a Sumo Logic query over up to 31 days, and reads monitors with their status and the account's open health events for failing collectors and sources. 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 disable named monitors so they send no alerts, save searches and create folders in the library, and pause or start scheduled views. Deleting a monitor or saved search is permanent.

In Memtro

What you can do with Sumo Logic in Memtro

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

What it does

  1. 01Log searches with a Sumo Logic query, the last hour by default and at most 31 days
  2. 02Raw messages, or the result rows of an aggregate query such as count by or timeslice
  3. 03Monitors with type, folder path, whether disabled, current status and when it last changed, filtered by words or status
  4. 04Open health events: failing or throttled collectors, sources and ingest budgets, with severity and when each began
  5. 05When asked and granted, disables named monitors so they stop alerting, or permanently deletes one with its configuration
  6. 06When asked and granted, saves a log search or creates a folder in the library, permanently deletes a saved search, and pauses or starts a scheduled view, which uses ingest capacity

Acts when asked

When you ask it to

These tools change something in Sumo Logic. 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. 01Disable chosen monitors so they stop alerting
  2. 02Delete a monitor (permanent)
  3. 03Save a log search to a library folder
  4. 04Delete a saved log search (permanent)
  5. 05Create a library folder
  6. 06Start a scheduled view
  7. 07Pause a scheduled view

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 Sumo Logic, choosing the same kinds; the tab shows Sumo Logic's own steps. Each event can start a job, with the event as its input. Sumo Logic sends a secret with every delivery, and one without it is refused.

Events and webhooks
  • 01Monitor alert: critical
  • 02Monitor alert: warning
  • 03Monitor alert: missing data
  • 04Scheduled search alert
  • 05Critical alert resolved
  • 06Warning alert resolved
  • 07Missing data resolved
In practice

Ask it like you would a colleague

Once Sumo Logic 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.

Sumo Logic + Memtro
  • What errors did the API log this morning?

  • How many timeouts per host has the checkout service had in the last hour?

  • Which Sumo Logic monitors are critical right now?

  • Is our logging pipeline healthy?

  • Disable the two disk-space monitors on the old staging hosts

01

Morning error check

Before stand-up the engineering lead asks what the API logged overnight. Memtro runs an aggregate search over the last eight hours and reports errors by host, with one host showing 3,400 of the 3,900 timeouts.

02

Quieting retired hosts

The old staging hosts at Acme were switched off last week and their monitors keep paging. Dan Fletcher asks Memtro to stop them. Memtro finds the three monitors by name and disables them, so they stop evaluating and send no alerts until someone re-enables them in Sumo Logic.

Teams

Where it fits

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

Better together

Works with

A record in Sumo Logic 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 withAccess ID, access key and deployment
  1. 1

    In Sumo Logic open your name → Preferences → Personal Access Keys and make a key. Copy the Access ID and Access Key, as the key is shown once. The key acts with its user's role, and a scoped key needs Run Log Search

  2. 2

    Log search through the API needs an Enterprise-type Sumo Logic account (Enterprise, Flex or a Credits trial). Monitors and health events work on any

  3. 3

    In Memtro open Connections → Sumo Logic, enter the Access ID and Access key, set Deployment to the code in your address (service.eu.sumologic.com is eu, service.us2.sumologic.com is us2, plain service.sumologic.com is us1) and connect

  4. 4

    Ask what errors the API logged this morning

Also works from

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

FAQ

Questions

Can Memtro change anything in Sumo Logic?+

Only when you ask, and only what it has been granted: disable chosen monitors so they stop alerting; delete a monitor (permanent); save a log search to a library folder; delete a saved log search (permanent); create a library folder; start a scheduled view; pause a scheduled view. 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 Sumo Logic 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 Sumo Logic 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 Sumo Logic?+

Access ID, access key and deployment. In Sumo Logic open your name → Preferences → Personal Access Keys and make a key. Copy the Access ID and Access Key, as the key is shown once. The key acts with its user's role, and a scoped key needs Run Log Search.

Can Sumo Logic 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 Sumo Logic, choosing the same kinds; the tab shows Sumo Logic'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 Sumo Logic in a few minutes

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

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.

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