Integration · Developer
AI agents for Sumo Logic
Search Sumo Logic logs: start a search job, follow it, read the matching messages or aggregated records, and clean it up; find monitors by status and read unresolved collection health events, with an access ID and key.
- Actions
- 7
- Read
- 6
- Write
- 1
Actions
What your agents can do in Sumo Logic
7 actions. Each one is a tool your agents can call and a step your workflows can run.
Read 6
Look things up. Nothing changes.
Start a log search
Starts a search job over a time range with Sumo Logic's query language, like _sourceCategory=prod/web error | count by _sourceHost or _index=app "timeout" | parse "user=*," as user.
Check a search
Reads a search job's state (NOT STARTED, GATHERING RESULTS, FORCE PAUSED, DONE GATHERING RESULTS, CANCELLED), messageCount, recordCount, histogramBuckets and any pendingErrors or pendingWarnings.
Read a search's log messages
Reads the raw log messages a non-aggregate search found, limit at a time from offset, in messages.
Read a search's results
Reads the rows of an aggregate search (one using count, sum, avg, timeslice and the like), limit at a time from offset, in records (each map of column to value), with fields.
Find monitors
Searches the monitors library, as a list in result.
List collection health events
Lists the account's unresolved health events, in data.
Write 1
Create, change or send.
Cancel and delete a searchDeletes data
Stops a search job and deletes its results.
A person can approve first
Any write action can be set to wait for a person's approval before it runs, so an agent asks before it changes anything. Actions that delete data ask first by default.
Connection
How it connects
Connect it once in the console, then give it to the agents and workflows that need it.
Enter the API credentials from your Sumo Logic account.
What you enter
- Access ID
- Access key
Settings
- Deployment
Kept safe
- Credentials are stored encrypted with your organization's own keys.
- They are opened only by the process that makes the call, at the moment it runs, and never go into a prompt or the browser.
- Calls go only to the tool's own servers.
Ideas
Ideas to start with
Starting points made only from the actions above. Mix them with any other tool your agents can use.
- 01
Ask about your Sumo Logic data
Ask a question in plain words. The agent can start a log search, check a search or read a search's log messages in Sumo Logic, then answers with what it found.
- 02
Let an agent update Sumo Logic
Have the agent cancel and delete a search in Sumo Logic as part of a larger task. Turn on approval and a person signs off on each change first.
- 03
Share what it finds in Slack
Give one agent Sumo Logic and Slack: it can start a log search in Sumo Logic and post a summary to a Slack channel in the same run.
FAQ
Sumo Logic and MyDeepAgents
Can MyDeepAgents connect to Sumo Logic?
Yes. The Sumo Logic connector has 7 actions: 6 read and 1 makes changes. Your agents can call them as tools, and your workflows can run them as steps.
How do I connect Sumo Logic?
Enter the API credentials from your Sumo Logic account. You'll need: Access ID and Access key. The connection also asks for: Deployment. Credentials are stored encrypted with your organization's own keys and are opened only at the moment of a call.
Can an agent change data in Sumo Logic without asking?
Only if you let it. Its one action that changes data can delete data, so it asks a person first by default.
Can I use Sumo Logic in workflows as well as agents?
Yes. Every Sumo Logic action also works as a step in a workflow, and the same connection serves your agents and your workflows.
Early access
Put Sumo Logic to work
Connect it in a few minutes, give an agent the actions it needs, and decide which changes wait for a person.