Use the Abnormal Events - Security Center incident type to alert operators to Security Center events that can cause system outage such as Application lost, Database lost, and so on.
Abnormal Events - Security Center incident type: functionality
For more information on the how the operator can monitor and manage the incident, see the Genetec Mission Control™ User Guide.
Abnormal Events - Security Center incident type configuration
The incident type is preconfigured with the following:
Abnormal Events - Security Center incident type: triggers
- Application lost
- Archiving stopped
- Cannot write on the specified location
- Database lost
- Invalid custom encryption values
- VRM connection failure
- Health event:
- Agent stopped
- Application disconnected unexpectedly
- Application stopped unexpectedly
- Archive backup failed
- Database automatic backup failed
- CPU usage high
- Database lost (Point of sale)
- Database lost
- Database space low
- Directory stopped unexpectedly
- Disk access unauthorized
- Duplicating archives failed
- Live server monitoring failed
- Main database lost
- Memory usage high
- Remaining archive disk space low
- Role stopped unexpectedly
- Server stopped unexpectedly
- Synchronization failed
- Unit time out of sync with time server
Based on your setup, you can add, remove or modify triggers as required. For more details, see Modifying incident triggers.
Abnormal Events - Security Center incident type: automation workflow
After the incident is triggered, the system waits to see if the error resolves itself. If it does, the system emails the Administrators and automatically closes the incident.
- Latest activity log
- Last event
- Incident trigger time
- Incident owner
- Incident sources
- Incident location
For more details, see Modifying incident automation workflow activities.
Abnormal Events - Security Center incident type: user procedure
The incident is configured with a dynamic procedure, that accepts operator response and directs system action accordingly.
The incident procedure steps include directives for the operators to put the incident on hold until resolution.
For more details, see Modifying incident user procedures.