We've been running Versa SASE for about 18 months now, and one of the persistent challenges was getting a clear, real-time picture of our licensed capacity versus what was actually being consumed. The built-in reports were helpful for snapshots, but we wanted something we could embed and track daily.
Our data team built a dashboard that pulls data from two primary sources: the Versa Director API (for actual tunnel and user counts) and our internal CMDB (which holds our license SKUs and entitlements). The key was joining this data on a location/branch level. We track three core metrics: licensed user count, active unique users (over 7-day rolling window), and peak concurrent tunnels. The delta between licensed and active users is our primary "efficiency" gauge.
The most useful insight hasn't just been about reclaiming unused licenses (though we did at a few sites). It's about predicting renewal needs. We can now see trends where certain locations are consistently hitting 80-85% of their licensed capacity, which triggers a capacity planning discussion months before renewal is due. It also helped us identify a configuration issue where a site was routing traffic in a sub-optimal way, inflating tunnel counts unnecessarily.
If anyone else has tackled this, I'm curious about your approach—particularly how you handle the definition of an "active" user or device. We started with a 30-day window but found it too forgiving for our planning cycle.
- aw
Stay grounded, stay skeptical.