Reports
The Reports tab shows what happened at the site over a period of time: how many alerts and detections there were, how quickly alerts were handled, when the site is busiest, and which cameras and zones raise the most alerts. Everyone who can sign in sees the tab.
Reports are read from the site database when you open them. Nothing leaves the site.
Filters
The filters at the top apply to every report on the tab.
| Filter | Choices |
|---|---|
| Date range | Last 24 hours, Last 7 days (the default), Last 30 days, Last 90 days, or Custom… with a From and To date. A custom To date includes that whole day. A range can be up to 366 days long. |
| Interval | How the charts over time are grouped: Hourly, Daily or Weekly. Auto picks one that suits the range. A chart can have up to 1,000 intervals, so for a long range pick a coarser interval. |
| Organization | All organizations, or one. Picking one limits the Camera list to its cameras. |
| Camera | All cameras, or one. |
Times and the site timezone
All dates, intervals and the busiest-hours grid use the site's timezone, the SITE_TIMEZONE your administrator sets. The tab's heading shows which timezone it uses, for example times in Asia/Dubai. Days start at local midnight, and summer time changes are taken into account.
If no site timezone is set, reports use UTC. See Site timezone.
What each report shows
Summary
A row of figures for the whole range:
| Figure | What it means |
|---|---|
| Alerts | Alerts raised in the range, with how many are still open. |
| Detections | Raw detections the edge nodes reported in the range, before any rule. |
| Dismissal rate | Dismissed alerts as a share of closed alerts. A high rate can mean a rule is too broad. |
| Median time to acknowledge | The typical wait for a first response, with the 90th percentile (p90) below it. |
| Median time to resolve | The typical time until an alert was resolved, with its p90. |
Alerts over time
Alerts per interval, stacked by the group you pick: Severity, Status, Camera, Event type or Workflow. The largest groups get their own color. The rest are added up as Other.
Detections by class
Raw detections per interval, by object class, for example person or car. This shows the activity the cameras see, whether or not it raised an alert.
Triage response times
How long alerts raised in the range waited:
- Time to acknowledge: until the first action that shows someone saw the alert. That is acknowledging it, or resolving or dismissing it straight away. Assigning an alert doesn't count, because it only routes it.
- Time to resolve: until the alert was resolved.
A bar chart groups the alerts into bands, from under 5 minutes to 24 hours and more. A table below gives the number of alerts, the median and the p90 for both. Alerts that nobody has handled yet are not counted.
Busiest hours
A grid of day of the week by hour of the day, in site time. The stronger a cell's color, the more activity in that hour. Pick Alerts or Detections as the source. Use it to plan staffing, or to check that the schedules in your detection profiles match real activity.
Top cameras
Cameras ranked by alerts raised in the range, with their open alerts and detections.
Top zones
Zones ranked by alerts, with the camera each zone belongs to and its open alerts. Only alerts from a workflow or detection profile that names a zone count here. See Zones.
Export a report as CSV
Each report has a CSV button. It downloads the data behind that report, with the filters you set, as a CSV file. The file name has the report name and the date range, for example argus-alerts-over-time-20261001-20261008.csv. Times in the file are in the site timezone.
Open the file in a spreadsheet, or load it into your own reporting tools.
When a report is empty
A report with nothing to show says so, for example No zone alerts in this range. Pick a longer range, or clear the Organization and Camera filters. If a report fails to load, click Retry.