Just logged into my Umbrella dashboard and got the banner notification. The "classic" dashboard is officially being deprecated on August 31st. They're pushing everyone to the new "Dashboard v2."
I've spent the morning poking around the new interface. The migration isn't just a fresh coat of paint—it's a complete restructuring of where to find things. For those of us who've built internal runbooks and monitoring around specific views in the classic dashboard, this is a significant operational change.
Has anyone started their migration process yet? I'm particularly curious about:
* **Custom report migration:** What happens to saved custom reports and scheduled exports? I don't see a 1:1 mapping of all the fields.
* **API endpoint changes:** If you're pulling data into a internal dashboard or a spreadsheet for cost allocation (like we do), have the underlying API endpoints shifted?
* **Performance data granularity:** In my quick tests, some of the historical data drill-down seems different. Can you still get the same level of detail for, say, last quarter's security activity by policy?
I'm already anticipating a few weeks of tweaking our internal documentation and FinOps tracking sheets. If anyone has found a smooth path or a hidden migration guide beyond Cisco's announcements, please share. The official docs are high-level and light on the gritty details we usually need.
Your point about the migration being a restructuring, not just a reskin, is exactly right. Based on the official documentation I've read, your concerns are valid.
On custom reports and API endpoints: they are not carrying over. You will need to rebuild custom reports in the new schema, and the API endpoints have changed. I'd recommend pulling a full export of any scheduled report configurations now, before your access is cut, as a reference point. The API shift means any internal dashboards or cost allocation spreadsheets will break if they rely on direct calls or old data connectors.
Regarding performance data granularity, my early testing shows a notable reduction in accessible historical detail for certain policy-level events. It appears designed for a more aggregated, executive view. If your runbooks depend on forensic-level data from last quarter, you may need to adjust your retention expectations or explore if that data is now only accessible via their Investigate module, which has separate licensing.
RTFM — then ask for the audit