lm-portal

Generate a LogicMonitor portal-wide health snapshot with alert statistics and collector status.

Updated Dec 13, 2025
One-click install
npx skills add https://github.com/ryanmat/mcp-server-logicmonitor --skill lm-portal
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lm-portal
Source: https://github.com/ryanmat/mcp-server-logicmonitor/tree/main/.claude/skills/lm-portal
Command: npx skills add https://github.com/ryanmat/mcp-server-logicmonitor --skill lm-portal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a comprehensive, portal-wide health snapshot for LogicMonitor, crucial for shift handoffs, daily standups, or on-call incident reports.

Core Features & Use Cases

  • Alert Analysis: Summarizes alert severity, trends, and identifies critical issues.
  • System Status: Reports on collector health and identifies any down devices.
  • Maintenance Awareness: Lists active scheduled downtimes (SDTs).
  • Root Cause Identification: Clusters alerts to pinpoint common factors and assesses alert noise.
  • Use Case: A system administrator can use this Skill at the start of their shift to quickly understand the overall health of their LogicMonitor environment, identify any immediate issues, and prioritize actions.

Quick Start

Provide a portal-wide health overview for the last 4 hours.

Frequently Asked Questions about lm-portal

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

FAQPage Schema
How do I generate a LogicMonitor portal health snapshot for shift handoffs?

A LogicMonitor portal health snapshot summarizes alert severity, collector status, active scheduled downtimes, alert clusters, noise scoring, and down devices, providing a configurable lookback window that defaults to 4 hours for shift handoffs.

What is included in a LogicMonitor system status and alert analysis report?

A LogicMonitor system status report includes alert severity trends, collector health, active scheduled downtimes, alert clusters for root cause identification, alert noise scoring, and down device detection.

Can I scope LogicMonitor alert statistics and incident reports to a specific time window?

Yes, you can scope LogicMonitor alert statistics to a specific time window by configuring the lookback period in hours, which defaults to a 4-hour window for incident reports.

How do I identify alert clusters and root causes in LogicMonitor?

Identify LogicMonitor alert clusters by generating a portal-wide health overview that groups alerts to pinpoint common factors, assesses alert noise scoring, and highlights critical issues for root cause analysis.

Does the LogicMonitor health overview check for down devices and collector status?

Yes, the LogicMonitor health overview checks for down devices and reports on collector status, allowing administrators to quickly identify environment issues and prioritize remediation actions during on-call incidents.