daily_brief
Run a morning health check across multiple Juniper devices in parallel. Detects alarms, interface down, syslog anomalies, and routing issues, providing a tiered summary of critical, warning, and ok status.
Instructions
Run a morning health check across multiple devices in parallel.
Checks per host (Phase 1):
show system alarms/show chassis alarmsshow interfaces descriptions— a physical interface is flagged[IF_DOWN]only when it has a description (Admin=up,Link=down) and itsLast flappedtime is withinsince_hours. Undescribed unused ports and chronically-down ports are suppressed (loopback / mgmt / internal logical units are also excluded).show log messages | last 200— alert patterns withinsince_hoursdual-RE redundancy — an explicit routing-engine fault is flagged
[RE_FAULT](skipped on SRX chassis clusters, whose facts misreport RE status; a failed cluster node raises chassis alarms instead)route_baseline(optional) — when > 0, a device whoseinet.0destination count differs from this value is flagged[ROUTE_BASELINE]. Scope withtags(e.g.tags=["main"], route_baseline=152), since full-table routers carry far more routes than access routers.
Syslog patterns watched: BGP state change away from Established, STP port role change, OSPF neighbor down, ARP address conflict, IF_DOWN.
since_hours defaults to 18 (≈ previous 15:00 for a 09:00 morning run).
Tags default to none (all routers); pass tags=["main"] to limit scope.
Output tiers:
CRITICAL — connection failure
WARNING — at least one anomaly found
OK — clean
Returns a Markdown summary with anomaly details for CRITICAL/WARNING hosts and a collapsed OK list.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| hostnames | No | ||
| tags | No | ||
| since_hours | No | ||
| route_baseline | No | ||
| max_workers | No | ||
| config_path | No |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |