Detection profiles
A detection profile tells Argus which detections matter for a camera. The detector sees every object class it knows. The profile filters those detections and decides when one is worth passing on to your workflows.
Each camera uses one profile. Many cameras can share a profile.
A profile has these parts:
- Target. Which object classes count.
- Trigger. The condition that must be met, such as "stayed longer than 3 minutes" or "entered a zone".
- Event type. Which kind of event a match creates, and so which workflows it reaches.
- Severity. How important a match is.
- Schedule. When the profile is active.
- Minimum confidence. How sure the detector must be before a detection counts.
A profile on its own does not raise alerts. A detection that passes the profile goes on to your workflows. You also need at least one enabled workflow with a Create Alert step. See Rules and workflows.
The default profile
Every site has a profile called Default / General. It passes every object class, fires immediately, has severity LOW and is active all day. You can't delete it. Cameras fall back to it if their profile is deleted or missing.
Create a profile
You need the admin role.
- Open Cameras & Edge Nodes and click Manage Profiles.
- Under Create New Profile, enter a Profile Name and, if you like, a Color Tag and notes. The colour labels the profile on camera cards.
- Under Target Detection, choose All Detectable Objects, or Selected Objects and pick one or more classes. The list shows every class your detector model supports.
- Under Trigger Conditions, pick a Trigger Type and fill in its settings. See Triggers.
- Pick an Event Type, or leave Default (Rule Trigger). See Event type.
- Pick a severity and an Operating Schedule. See Schedule.
- If you like, set a Minimum Confidence. See Minimum confidence.
- Click Save Detection Profile.
- On each camera that should use it, pick the profile in the camera's Profile list.
Argus derives a key from the profile name, for example loading-bay-dwell for "Loading Bay Dwell". If you create a profile with the same name as an existing one, the existing profile is updated.
Changes take effect within about 30 seconds.
Describe a profile in plain words
At the top of Manage Profiles, the AI Natural Language Rule Assistant turns a sentence into a profile draft, for example "Alert me when a person enters the loading dock zone after 22:00".
- Type what you want. Pick a camera under Context so the assistant knows that camera's zones, or leave General (All Cameras).
- Click Generate Rule.
- Read the Interpreted Detection Rule. If the assistant needs more detail, it asks under Clarification Needed.
- Click Create Profile to save it as it is, or Edit / Customize to load it into the form and change it first.
The assistant uses the same local model as the Copilot. It only drafts: nothing is saved until you create the profile. Check the draft before you save it.
Triggers
| Trigger | Fires when | Settings |
|---|---|---|
| Immediate | A target object is detected. | None. |
| Dwell Time | A tracked object has been seen for longer than the duration you set. | Operator (> or >=) and Duration (Seconds). |
| Object Count | The number of target objects seen on the camera in the last 4 seconds meets the count you set. | Operator (>, >= or ==) and Object Count. |
| Zone Entry | A tracked object moves into a zone. | Zone Name / ID (Optional). |
| Zone Exit | A tracked object moves out of a zone. | Zone Name / ID (Optional). |
How each trigger behaves:
- Dwell Time measures from the first time Argus saw the tracked object. It fires once per object.
- Object Count fires at most once every 10 seconds per camera, so a crowd that stays doesn't raise an alert every frame.
- Zone Entry fires once each time an object moves into the zone. Zone Exit fires once each time it moves out.
- For the zone triggers, enter the name of a zone you drew on the camera, or leave the field empty to use any of the camera's zones. Draw zones with Edit Zones on the camera's card. See Zones.
Event type
The event type decides which kind of event a match creates. A workflow that is set to an event type only runs for events of that type. Leave Default (Rule Trigger) to create untyped rule events, which every workflow can match. See Event types.
Severity
| Severity | Use it for |
|---|---|
LOW | Information and analytics. |
MEDIUM | Something that needs attention. |
HIGH | An important safety or security event. |
CRITICAL | An urgent incident. |
The severity is stored on the rule event and shown on the alert, unless the workflow's Create Alert step sets its own severity.
Schedule
| Schedule | Active |
|---|---|
| All Day | Always. |
| Business Hours | 08:00 to 22:00. |
| After Hours | 22:00 to 08:00. |
| Custom windows | Only inside the windows you add. |
For Custom windows, click Add window for each window, pick its days and set a start and end time. An end time earlier than the start wraps past midnight: a Friday window from 22:00 to 06:00 also covers Saturday until 06:00. A window whose start and end are the same covers the whole day. You can add up to 28 windows.
Schedules use the site's local time, set by your administrator with SITE_TIMEZONE, for example Asia/Dubai. Without it they use UTC. See Install.
Minimum confidence
The detector gives each detection a confidence between 0 and 1. Detections below the profile's minimum confidence are ignored for this profile, before any trigger counts them.
By default a profile uses the site-wide default, 0.25 unless your administrator changed it. Turn on Minimum Confidence to set a value for this profile. A higher value means fewer false alarms but more missed detections.
Limits to know
- Dwell timers and "already fired" markers are kept in the rule engine's memory. If the
site-rule-engineservice restarts, they start again. An object already in view can then raise a new alert. - The rule engine forgets when it first saw a tracked object about 5 minutes after that first sighting. Keep Dwell Time durations under 5 minutes (300 seconds). Longer durations don't fire reliably.