This page shows how to trace what happened to one alarm and who did what.
Who it is for: Users with the role Admin who supervise operators. Setting up sites and devices is described in Setting Up Sites.
Watch:
GC Surge records what happens to each alarm and what users do.
Area | Examples |
|---|---|
Each alarm | Received, result of NOVA99x, decision, operator, times, what was forwarded. |
Operator session | Shift start, pause, resume, automatic pause because of inactivity, end of shift, logout. |
Supervisor actions | Assign, reassign, release, forward now. |
Configuration | Changes to sites, devices, forwarding and settings. |
Column | Meaning |
|---|---|
Date & time | When it happened. |
Action | What was done. |
Action status | The result of the action. |
User | Who did it. |
Category, Sub category | The kind of action. |
Source entity | What the action was applied to. |
Device, Site | Where it applies. |
Question | Where to look |
|---|---|
Who decided this alarm, and when? | Recordings > alarm > Alarm workflow |
Was this alarm forwarded, and by whom? | Operator handling status in the alarm detail |
Why was an alarm forwarded without an operator? | Audit logs at that time: were operators paused, inactive or logged out? |
Who changed the forwarding of a site? | Audit logs, filter by site |
How often was an operator set to inactive? | Audit logs, filter by user |
Symptom | Cause | What to do |
|---|---|---|
Audit logs shows no records | No actions in the time range, or a filter is set. | Extend the time range. Clear the filters. |
You cannot find an old alarm | The time range does not include it. | Set a custom range around the date. |
Thank you — your feedback goes to the team that owns this page.
