skills.rest
ryanmat
ryanmatCOMMUNITY
Explore all skills by this author →
GitHub

lm-remediate

Diagnose LogicMonitor alerts and execute Ansible playbooks for remediation.

Updated Dec 13, 2025
Search Tags:#automation#troubleshooting#remediation#alerting#ansible#logicmonitor
One-click install
npx skills add https://github.com/ryanmat/mcp-server-logicmonitor --skill lm-remediate
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: lm-remediate
Source: https://github.com/ryanmat/mcp-server-logicmonitor/tree/main/.claude/skills/lm-remediate
Command: npx skills add https://github.com/ryanmat/mcp-server-logicmonitor --skill lm-remediate

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of diagnosing alerts within LogicMonitor and executing remediation actions using Ansible Automation Platform, bridging the gap between monitoring and automated resolution.

Core Features & Use Cases

  • Automated Diagnosis: Gathers comprehensive context around an alert, including device health, related alerts, and recent changes.
  • Playbook Discovery & Execution: Identifies and runs appropriate Ansible playbooks for remediation.
  • Verification & Documentation: Confirms if the remediation was successful and logs the actions taken.
  • Use Case: When a critical server alert fires, this Skill can automatically analyze the issue, find a relevant Ansible playbook to restart a service, execute it in a dry-run first, and then perform the live remediation, finally documenting the entire process.

Quick Start

Use the lm-remediate skill to diagnose and remediate alert ID 12345.

Frequently Asked Questions about lm-remediate

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate LogicMonitor alert remediation with Ansible?▼

LogicMonitor alert remediation is automated by gathering alert context, assessing blast radius, discovering relevant Ansible playbooks, and executing them. The process verifies the resolution and logs actions taken for complete documentation.

Can I run Ansible playbooks in a dry-run before live remediation of server alerts?▼

Yes, live remediation is preceded by a dry-run execution of the Ansible playbook. This allows you to validate the proposed fix for a critical server alert before applying it to the production environment.

What context does automated alert diagnosis gather for troubleshooting?▼

Automated alert diagnosis gathers comprehensive context including device health, related alerts, and recent changes. This contextual data helps assess the blast radius and identify the correct remediation playbook.

Does LogicMonitor alert remediation require Ansible Automation Platform to function?▼

Yes, the Ansible Automation Platform is required to execute remediation actions. The Skill integrates with it to discover and launch appropriate playbooks to resolve the diagnosed LogicMonitor alerts.

What is the best way to verify if an automated Ansible remediation fixed a LogicMonitor alert?▼

Verification is handled automatically by the Skill after executing the Ansible playbook. It confirms whether the remediation successfully resolved the LogicMonitor alert and documents the entire process for review.

Related Skills

Explore More Software Engineering Skills→
ryanmatryanmat

lm-triage

Automates LogicMonitor alert triage by severity, noise scoring, correlation, and blast radius assessment.

Community
Advanced
skwuwuskwuwu

gvm_audit

Verify GVM audit log integrity and export compliance reports.

Community
Intermediate
nist0nist0

logs-alerts

Analyze system logs to identify symptoms and design alert rules.

Community
Intermediate
ryanmatryanmat

lm-health

Assess LogicMonitor device health via metrics, anomalies, alerts, and topology.

Community
Advanced