Troubleshoot a Palo Alto Networks fleet from one screen

Firewall Fleet Health is a visualization and troubleshooting tool that works alongside Panorama. It reads your fleet through a read-only API account and puts every firewall, tunnel, SD-WAN path and recent change on one dashboard, so a complaint like "the internet is slow in Dayton" leads to the failing site, link or change in a few clicks. Panorama stays where you manage policy and push configuration.

Why does finding the broken site take so long?

A management console is built to configure firewalls. Asking it a fleet-wide question, such as which site is dropping tunnels or which application is filling a link, means several steps per device group and time range: pick the scope, open the right monitor or log view, set the filter, read the result, then repeat for the next group.

Fleet Health collects the same facts on a schedule and keeps them, so the answer is already on the page when the ticket arrives.

The console

  1. Pick the device group
  2. Open the monitor or log view
  3. Set the time range and filter
  4. Read the result
  5. Repeat for the next device group

Fleet Health

  1. Open the Overview. The site with the problem is already yellow or red.
Answering "which site is broken?" across a fleet, step by step.

What does Fleet Health show instead?

Each view answers one question across the whole fleet at once.

Overview
Every firewall as a green, yellow or red tile beside the SD-WAN hub links, so one bad site stands out from the rest of the fleet.
SD-WAN
Latency, jitter and loss per path, a hub-by-site matrix, and a tunnel drops heatmap that says whether a hub or a site is the cause.
Bandwidth by application
Which applications are using each site's links, from the firewall's own sessions.
Events and changes
A searchable firewall event log and config changes with before and after side by side, secrets masked.
Device page
HA state and sync, last reboot with its reason, software versions, certificate and subscription expiry, CPU, memory, sessions and throughput.

Which numbers are hard to get today?

The one most teams miss is per-path SD-WAN latency, jitter and loss history, the kind of view usually sold as a premium cloud add-on. Fleet Health includes it, keeping 7 days of 5-minute detail and 13 months of daily trends.

It also reads BGP peers and flaps, IKE failures, WAN interface errors and drops, global drop counters, and GlobalProtect users.

How does it work alongside Panorama?

With Panorama, Fleet Health uses one read-only API account and Panorama's certificate, and asks each managed firewall for its live numbers through Panorama. The dashboard never changes configuration on Panorama or the firewalls.

Without Panorama, direct mode reads each firewall's own API instead, so the same views work for a fleet with no management server.

How far back can I look?

Fleet Health keeps 18 months of firewall events and config changes, 13 months of daily trends, 30 days of tunnel status, and 7 days of 5-minute detail. "What changed before this started?" has an answer even when the change was months ago. On the Events tab, set the event log or the config change list to look back up to 18 months.

See it on a fleet

See the fleet views on a demo fleet of 36 firewalls, or book a walkthrough with ROC Cybersecurity.