Below are details on each of the below fields seen on the Dashboard

Sites with Low Availability

Any site that records an availability lower than 50%, for the time-period that’s being queried, will be counted against this field in the Dashboard. You can drill down further by clicking to the link (that’s activated on this value) to get a list of these sites. This is just to help users be aware of any site that’s low on availability or is not available during the time-period.

Sites with Dataplane Downtime

We infer that the Dataplane, for a site, is “down” if all the SLAs towards all the remote sites is down – for example, Branch X has SLA up towards the controllers, but has SLA down towards all its remote sites, then the counter for “dataplane down” (we maintain a counter at VOS for dpdown) increments for each such instance. The branch sends this counter value, as an Analytic log, which is then stored in the Cassandra DB under connectionsStats table.

Sites that record a value for dpdown (> 0) will be accounted for in the Dashboard display of “Sites with Dataplane downtime”, so that the customer is aware of the sites which lost complete dataplane connectivity to all its remote sites during the time-period being queried.

Sites with Critical and Major Alarms

Any site which has active critical or major alarms will be counted/listed against this field on the Dashboard, this helps the customer get a quick view of sites that have a problematic condition ongoing. One can list these sites by clicking on the link that would appear against this field.

Sites with Disconnects

A “branch disconnect” alarm is generated by the Controller when it loses all SLAs towards a site, in other words when a site goes completely unreachable from the perspective of a controller. Sites which register “branch disconnects” on a controller, will be counted/listed against this field on the Dashboard. Each site maintain a counter, every time it loses SLAs on all the paths towards a controller, and sends this counter to the Analytics – this counter is used as the reference to display the sites with disconnects on the Dashboard for the time-period being queried. Loss of reachability to a controller is a critical event and this field helps the customer evaluate such sites.

Sites with Violations

Every SLA dapathdown event (when SLA goes down on a path) or SLA violation event (when there is a SLA profile breach encountered on a path owing as per it’s affiliation to a forwarding policy) is counted against a counter on the branch, which is then sent to the analytics. This field will reflect all branches with positive counters (> 0) for the time period being queried, and these sites and the number of events counted can be seen by clicking on the link against this field.

Sites with Threats

The branch will record a count for all IDP, AV, DosThreat, Url-filtering, ip-filtering and file-filtering, logs that are generated, and pass on this count to the Analytics every 5 mins. This field reflects all the sites with a positive count, and you can see the number of events against each site when you click on the link. In the next 22.1.3 hotfix we will count only the threat logs with critical severity (currently we are counting all logs).