Skip to content

berkeleyo/logicmonitor-hybrid-monitoring

Repository files navigation

LogicMonitor Hybrid Monitoring — Hyper‑V, AWS EC2, and Google Cloud (CPU, Memory, Uptime) 🚀

Redaction Status

Redaction statement: This repository contains no secrets, credentials, tenant IDs, public IPs, hostnames, or direct org identifiers. All placeholders are fictional and safe to publish.

✨ What this is

Enterprise‑grade, clean, production‑ready documentation and starter automation for monitoring Hyper‑V, AWS EC2, and Google Cloud resources in LogicMonitor with an emphasis on CPU, memory, and uptime/runtime alerting.

Example scope replaced with this project’s scope: LogicMonitor + Hyper‑V + EC2 + Google Cloud for CPU/Memory/Uptime alerts.


📚 Repository layout

.
├── README.md
├── RUNBOOK.md
├── .gitignore
├── docs/
│   ├── OVERVIEW.md
│   ├── ARCHITECTURE.md
│   ├── CUTOVER_CHECKLIST.md
│   ├── ROLLBACK.md
│   └── SECURITY.md
└── scripts/
    ├── install-lm-agent-windows.ps1
    ├── install-lm-collector-linux.sh
    ├── add-aws-account.json
    ├── gcp-custom-role.json
    └── create-device-group.sample.json

🧭 Delivery lifecycle

flowchart LR
    A[Discover] --> B[Design]
    B --> C[Build]
    C --> D[Test]
    D --> E[Cutover]
    E --> F[Operate]
    F --> G[Improve]
Loading

Stages

  • Discover: Inventory Hyper‑V hosts/VMs, EC2 instances, and GCP compute. Confirm alert policies for CPU, memory, uptime.
  • Design: Choose collection methods (agent/WMI/SNMP/Cloud integrations). Define device groups, naming, and escalation chains.
  • Build: Configure LogicMonitor collectors/agents, AWS/GCP integrations, and device groups.
  • Test: Validate metrics & alert thresholds; run synthetic load where safe.
  • Cutover: Enable alert routing to production contacts/on‑call.
  • Operate: Review dashboards, triage incidents, and refine thresholds.
  • Improve: Iterate on noise reduction, SLOs, and automation.

🧩 Architecture (high level)

graph TD
    subgraph OnPrem["On Prem"]
        HV1["Hyper-V Host(s)"] -->|WMI/Agent| COLLECTOR1["LM Collector/Agent"]
    end

    subgraph AWS
        EC2["EC2 Instances"] -->|CloudWatch + API| LMAWS["LM AWS Integration"]
    end

    subgraph GCP
        GCE["GCE VMs"] -->|Cloud Monitoring API| LMGCP["LM GCP Integration"]
    end

    COLLECTOR1 --> LM["LogicMonitor SaaS"]
    LMAWS --> LM
    LMGCP --> LM

    LM -->|Alerts| ONCALL["On-call / ITSM"]

Loading

✅ Goals

  • Standardize CPU, memory, and uptime alerts across Hyper‑V, EC2, and GCP.
  • Provide a cutover checklist and rollback plan.
  • Ship minimal scripts and JSON examples suitable for production use (with placeholders only).

🚀 Quick start

  1. Read docs/OVERVIEW.md and docs/ARCHITECTURE.md.
  2. Follow RUNBOOK.md end‑to‑end in a non‑prod environment.
  3. Customize thresholds, device groups, and escalations in LogicMonitor.
  4. Use the scripts/ as starting points for agent/collector install and API calls.

🔒 Security & redaction

  • No keys, tokens, account numbers, or IPs in this repo.
  • Replace placeholders like YOUR_SUBSCRIPTION, YOUR_ACCOUNT_ALIAS, and example@domain.tld.
  • Follow docs/SECURITY.md before enabling production alerts.

📄 License

This repository is provided “as‑is” without warranty. Use at your own risk.

About

LogicMonitor setup for hybrid infrastructure with useful checks.

Topics

Resources

Security policy

Stars

Watchers

Forks

Packages

No packages published