Analytics
What Virtik's Analytics module reports, how its views are organised, how access to figures is controlled and audited, and which views were and were not verified.
- Versione
- 0.2
- Ultimo aggiornamento
- Disponibilità
- Verificato in test controllati
Sfoglia la documentazione
In questa pagina
Questo documento è attualmente pubblicato solo in inglese. Leggi la versione inglese di riferimento
Analytics is Virtik's reporting module. It reports on what the other modules record (incidents, response, cameras, patrols, communication, training, people) for one site or across the sites an organisation has access to. Every figure it shows is read from records in Virtik.
The views
Analytics opens on the Dashboard. The navigation also holds cross-module and per-site views, a view for each of several modules, and reports.
| Group | Views |
|---|---|
| Global | Dashboard (the default), Cross-Module Analytics, Security Sites. |
| By module | An analytics view for each of Detection, Training, Prevention, AI Agents, Team, Patrol, Communication and CSR / ESG. |
| Reports and registers | Report Center, Duty Log, Security Register and Audit Trail. The Duty Log and the Security Register are operational registers rather than reports. |
The Dashboard has six tabs: Overview, By Site, SLA Tracking, Incident Trends, Benchmark and Data Health. It offers Save View, Export and Refresh. Overview, By Site and Incident Trends have sub-views: Operational Snapshot, Exceptions and Readiness; Performance, Incidents, Cameras and Patrols; and Volume, Severity, Type, Response and Resolution.
Data Health
Data Health says, source by source, whether the figures can be trusted. For each source it shows its status (Readable, Not readable, Not present or Query failed), its records, how many fall in the period, and the newest. In that table a source that cannot be read shows "—" rather than 0. Elsewhere on the Dashboard, current-state counts that could not be read are shown as zero, with a note saying so.
Metrics
Each metric is defined in a catalogue with its source, how it is calculated and its direction. Some are marked as not available or not configured rather than shown empty. The metric calculations are defined in the database.
Exports and reports
The Dashboard exports the rows behind the active chart as a CSV file; for several views that is the incident time series. Report Center produces reports as PDF, Excel and CSV. It also lists three things as "not available": scheduled report delivery, cross-module AI synthesis and a report archive. Cross-Module Analytics shows links between records that can be proven (an incident that came from a detection, for example); it does not show statistical correlations.
Who can see what
- Figures are limited to the sites a person has been given access to, with these exceptions: Data Health, the Training view, the Prevention view and the AI Agents view are organisation-wide and offer no site filter, and the Communication view offers no site filter and counts only messages tagged to a site, plus organisation-wide broadcasts. An organisation switch discards what was loaded for the previous one.
- Administrators and editors must have completed two-step verification to read Analytics; viewers can read it without.
- If a person lacks access, the page says so rather than showing zeros.
- The Audit Trail is the organisation's audit log, with the actor and role for each event. Reading it needs a specific permission and two-step verification for every role, viewers included.
Opening is recorded for the Dashboard, Cross-Module Analytics, the Audit Trail and Report Center, and exporting is recorded for the Dashboard and Report Center. The other module views do not record. If a recording cannot be written, the screen does not tell you.