T-ISP-026 · CPU / Memory Triage Collector

Sweep the fleet for control-plane health: poll CPU, memory, and top processes via SSH, rank devices by pressure, and flag those above warning/critical thresholds for NOC triage.

Cisco IOS/XE

Cisco IOS-XR

Juniper Junos

Arista EOS

Open in Generator Open in Platform

You're viewing a preview

The full script, parameters, and execution console are available with a free account.

Already have access? Sign in →

Capabilities

CPU + memory poll
Top-process capture
Warn/critical thresholds
Pressure ranking
Concurrent collection
JSON triage report

Required inputs

Parameters the script accepts. Defaults shown; some are vendor- or context-gated.

Parameter	Type	Default	Notes
CPU warn (%) cpu_warn	number	75	—
Memory warn (%) mem_warn	number	80	—

Hint 1 — Name your vendors and OS versions

Mention the exact platforms you run (Cisco IOS/XE, Cisco IOS-XR, Juniper Junos, …) so the generated isp & peering logic uses the right CLI/NETCONF syntax.

Hint 2 — State your real thresholds

Provide concrete values for CPU warn (%), Memory warn (%) instead of the defaults — they shape what counts as a fault.

Hint 3 — Prioritize the checks you need

This tool can cPU + memory poll and top-process capture. Ask for the subset relevant to your incident to keep output focused.

Hint 4 — Describe your inventory format

Tell the assistant whether your device list is CSV, YAML, or JSON and which columns it has, so parsing matches your data.

Sample inventory schema

Authoritative shape of the device/policy data this script consumes.

No bundled inventory sample. The script accepts standard device lists (CSV/YAML) with hostname, mgmt IP, vendor, and credentials.

Expected output

Reference terminal output the script should produce — used as a stylistic and structural target.

terminal

2026-06-15 19:00:00 INFO  Polling 47 devices (cpu_warn=75 mem_warn=80)
2026-06-15 19:00:03 WARN  core-rtr-02: CPU 91% CRITICAL (top: bgp_router)
2026-06-15 19:00:03 WARN  pe-rtr-09: MEM 84% WARN
2026-06-15 19:00:03 INFO  Triage report written to triage.json (2 flagged)