Recordings lists every alarm that GC Surge received: filtered alarms, alarms decided by operators and alarms forwarded automatically.
Watch:
Step 1: In the top bar, click Recordings.
Step 2: In the top bar, click the time range (for example Last 24 hours) and choose a period.
Step 3: Choose the view: Card view (one card per alarm with its picture, its result, the camera and the time), List view (table) or Audit logs (Audit & Traceability).
Step 4: Use All sites, All cameras and Search recordings to narrow the list. Click More filters (the sliders icon) for:
Filter
Values |
|---|
Operator | One of your operators. Admins who handled alarms in Operator mode are listed too. |
Operator decision | Real alarm, Not an alarm, Forwarded, no operator and Forwarded by admin |
NOVA99x | True alarms, False alarms |
Modality | Thermal, Optical |
System action | Passed to ARS, Not passed |
Status | Open and Closed |
Step 5: Total alarms shows the number of results. Clear removes the filters.
The list shows Current image, Site, Device, Sensor, Date, Acknowledged status and Modality. Click Show more for further details of a row.
In Recordings, every alarm shows a colored status label. The status tells you how the alarm was handled and whether it reached your alarm system.
Status | When it appears |
|---|---|
Filtered alarm | NOVA99x classified the alarm as not real and GC Surge closed it. No operator saw it. |
Not an alarm | An operator closed it as Not an alarm. |
Sent to ARS | An operator decided Real alarm and every alarm reception destination accepted it. |
Real alarm · no ARS receiver | An operator decided Real alarm but no destination is configured. |
Real alarm · ARS delivery failed | An operator decided Real alarm but every destination failed after retries (for example unreachable or timed out). |
Forwarded, no operator | No operator was available. GC Surge closed it and every destination accepted it. |
Forwarded by admin | An admin forwarded it with Forward now and every destination accepted it. |
No operator · no ARS receiver | No operator was available. The queue timeout closed it and no destination is configured. |
No operator · ARS delivery failed | No operator was available. GC Surge closed it on time but every destination failed after retries. |
Partially sent to ARS | At least one destination accepted it and at least one failed. |
Sending to ARS… | GC Surge is still forwarding it, retries included. This usually takes less than a minute. |
Open | Not handled yet: waiting in the queue or assigned to an operator. |
Closed | Closed for a reason that matches none of the statuses above. |
Question | Filter |
|---|---|
Which real alarms did we send today? | System action: Passed to ARS |
What was forwarded without an operator? | Operator decision: Forwarded, no operator |
Which alarms were filtered on site X? | Site X, NOVA99x: False alarms |
What did operator A decide last night? | Operator: A, time range of the night |
Which alarms are still open? | Status: Open |
Watch:
Step 1: In List view, click Show more in the alarm's row. In Card view, click the alarm card. The panel Alarm details opens.
Step 2: Alarm images: Pre-alarm, Alarm, Post-alarm and GIF. Alarm sequence plays them in order, with a PRE-ALARM · ALARM · POST-ALARM bar.
Step 3: Alarm workflow shows the history of this alarm:
Line | Meaning |
|---|---|
Event received at | When GC Surge received the alarm. |
NOVA99x filter | The result of the filter, for example "Real alarm". |
Operator | Who decided, or "System: no operator available". When an admin used Forward now, the line is called Admin. |
Handled at | When the decision or the automatic forward happened. |
Operator handling status | The result, for example "Forwarded to ARS · no operator". |
Step 4: ARS delivery shows whether the alarm reached your alarm system. Each destination (Webhook or DC09) is listed with its own result:
Result | Meaning |
|---|---|
Delivered to ARS | Every destination received the alarm. |
Partially delivered: at least one destination failed | Some destinations received the alarm, at least one did not. |
Not delivered: every destination failed | No destination received the alarm. |
Not delivered: no alarm receiver configured | No destination is set, so the alarm was not sent. |
Sending to ARS, retrying failed destinations | GC Surge is still sending. It tries a failed destination up to 3 times. If delivery is still pending after 5 minutes, it shows as failed. |
Per destination you see delivered, or failed with the reason (unreachable, timed out, invalid destination or rejected by receiver).
Step 5: Click View ZenMode event to see the whole site event as the operator saw it.
alarm-events-export-, followed by the date and time.You can export up to 24 hours at a time. For a longer time range, Export is disabled. Export day by day.
Symptom | Cause | What to do |
|---|---|---|
No results | The time range or a filter excludes everything. | Click Clear. Set Last 24 hours. |
Export is disabled | The time range is longer than 24 hours. | Choose 24 hours or less. For a longer period, export several times. |
"Could not export alarm events. Try again." | A temporary problem. | Try again with a shorter period. |
"There are no ZenMode events for open alarms" | The alarm is not decided yet, so there is no site event to show. | Open it again after the decision. |
An alarm has no pictures | The device sent none. | Check the alarm settings of the device. |
An alarm shows ARS delivery failed or No ARS receiver | A destination did not accept the alarm, or no destination is set. | Open the alarm and read the reason under ARS delivery. Check the destination in Settings > Alarm reception or in the site or device forwarding. |
Thank you — your feedback goes to the team that owns this page.