Cortex Data Lake: firewall logs in one place

Metrics, device status, and onboarding lived in three separate apps, so finding why a firewall stopped sending logs meant hopping between them, with no link between a drop in logs and the disconnection that caused it.

I mapped the troubleshooting journey with engineering and sales engineers, then prioritized every metric on the new dashboard against real customer interviews before it shipped.

Each widget was written up before it was drawn: what it is for, what data answers that, and what should be true by default. Open questions stayed on the board as sticky notes rather than being settled quietly, which is what made the reviews with engineering worth having.

The page itself was drafted as three arrangements rather than one, so the discussion stayed on which layout served a troubleshooting job instead of on whether any single number deserved the space.

Every firewall's health now lives on one screen, tied directly to the connection history behind it, with inventory and onboarding folded into the same app.