A workflow for connecting LogicMonitor alerts to automated responses through EDA Controller and Ansible Automation Platform. EDA Controller receives events and can start automation jobs.

Use it to review alert patterns or a device, test connections to EDA Controller and Ansible Automation Platform, configure event streams and rulebook activations, and verify the automation chain.

It helps turn recurring alert patterns into checked, repeatable responses instead of requiring an operator to react manually each time.

lm-eda — Skill for Claude Code by ryanmat/mcp-server-logicmonitor

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add ryanmat/mcp-server-logicmonitor --skill lm-eda

Clone the repo

git clone --depth 1 https://github.com/ryanmat/mcp-server-logicmonitor

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/ryanmat/mcp-server-logicmonitor/lm-eda/github.svg)](https://agentmods.dev/skills/ryanmat/mcp-server-logicmonitor/lm-eda)

Your own site

<a href="https://agentmods.dev/skills/ryanmat/mcp-server-logicmonitor/lm-eda"><img src="https://agentmods.dev/badge/skills/ryanmat/mcp-server-logicmonitor/lm-eda/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/ryanmat/mcp-server-logicmonitor/lm-eda"><img src="https://agentmods.dev/badge/skills/ryanmat/mcp-server-logicmonitor/lm-eda.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 18 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,565 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00018	$0.01565
Opus 5.5	$0.00007	$0.00626
Sonnet 5.5	$0.00004	$0.00313
Haiku 4.5	$0.00002	$0.00156

Measured 2mo ago against content hash af5033325a44, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

lm-eda scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

contrib/eda/skills/lm-eda/SKILL.md · 178 lines

How it starts

The opening of the file, as written. The whole thing — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Event-Driven Alert Automation

You are an automation engineer setting up event-driven alert response using LogicMonitor + EDA Controller + Ansible Automation Platform. Your job is to analyze alert patterns, configure event streams, find or create rulebook activations, and verify the automation chain works end to end.

Argument Parsing

Parse the user's input to determine the automation target:

Alert pattern -- A datasource or datapoint name pattern to automate (e.g., "disk full", "cpu high", "service down").
Device name -- A device to review alert history and recommend automation.
No argument -- Ask the user what alert pattern or device to automate.

Workflow

Execute these steps in order. Present findings at each step before moving on.

Step 0: Connection Check

Call test_eda_connection to verify EDA Controller is reachable.

If the connection fails, stop immediately. Report the failure and suggest checking EDA_URL, EDA_TOKEN, and network connectivity.
If the connection succeeds, also call test_awx_connection to verify AAP Controller is reachable (EDA triggers AAP jobs).

Step 1: Alert Pattern Analysis

Analyze the alert landscape to identify automation candidates.

Call get_alerts with filters matching the user's target pattern.
Call get_alert_statistics to understand severity distribution and frequency.
Call correlate_alerts to identify clusters of related alerts.

Present the analysis:

Alert volume and frequency for the target pattern
Severity breakdown
Top affected devices
Recurring patterns suitable for automation

Step 2: Existing Automation Inventory

Check what EDA infrastructure already exists.

Call get_eda_event_streams to list configured webhook endpoints.
Call get_eda_activations to list active rulebook activations.
Call get_eda_projects to list available projects with rulebooks.
Call get_job_templates with a name filter to find matching AAP templates.

Present what is already in place:

Event streams that could receive LM webhooks
Active rulebook activations and their status
Available rulebooks that match the alert pattern
AAP job templates that could be triggered

Read the full file on GitHub · 178 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2mo ago First seen · 178 lines · 18 tokens per session scan A af5033325a44

Subscribe to this mod's changes

lm-eda is a skill published in the GitHub repository ryanmat/mcp-server-logicmonitor (1 stars, last pushed 7d ago), licensed MIT. It adds 18 tokens to every session and 1,565 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Cloud DevOps and cloud

lm-eda next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
lm-edaryanmat/mcp-server-logicmonitor	Skill	1	7d ago	MIT	A	18	Claude Code
gke-compute-classesgoogle/skills	Skill	22k	yesterday	Apache-2.0	A	83	Claude Code, Codex
gke-reliabilitygoogle/skills	Skill	22k	yesterday	Apache-2.0	A	85	Claude Code, Codex
gke-workload-securitygoogle/skills	Skill	22k	yesterday	Apache-2.0	A	171	Claude Code, Codex
cloud-architectJeffallan/claude-skills	Skill	12k	7d ago	MIT	A	71	Claude Code
nemo-automodel-launcher-configNVIDIA/skills	Skill	3.9k	yesterday	Apache-2.0	A	30	Claude Code
azure-mgmt-botservice-dotnetmicrosoft/skills	Skill	3.2k	yesterday	MIT	A	78	Claude Code