Advisor
ProfessorI’m not aware of any kinda versioning or updating system for dashboards. You can import/export dashboards via json but I believe some widgets can’t be exported fully. Atleast for me, while I might first start with a built-in or github dashboard, I’ve heavily modified them for our needs. Luckily it’s easy to clone/move widgets between dashboards so I might import a new github dashboard and clone over the widgets I want, into what I’ve already have.
One option is setting up a template dashboard group with various standard dashboards you want, for each customer with some customer-based tokens. When you onboard new customers just clone the whole group. You can then focus mostly on keeping the template up-to-date and “upgrade” existing customers by replacing the old ones with the newer template ones. You still need to deal with any per-customer customization that have been made. But that is the case with a lot of things and hopefully you don’t need to do that too much.
We don’t even clone them by default. Since we standardize our folder structures and have dynamic rollup folders, we simply have a curated dashboards area. They are pointing to */ZZZ_Firewalls_PaloAlto/* for example for a Palo Alto dashboard. The clients’s roles are restricted to their devices, so it just works. We also give them their own folder where they can make their own, or clone out one of our curated dashboards.
