If you need to add custom incident priorities and states, or change the incident state transition rules in your system, you can do so by configuring the Incident Manager role settings in Genetec Mission Control™.
What you should know
The Incident Manager role is automatically created when you upgrade your Security Center system to Mission Control, and is hosted by default on your main server. There can be only one instance of this role on your system.
Procedure
- From the Config Tool home page, open the System task and click the Roles view.
- Select the Incident Manager role, and click the Resources tab.
-
(Optional) Add secondary servers to the Incident Manager role to support
failover.
For more information, see Setting up role failover.
-
Configure the Incident
Manager database.
The default database name is IncidentManagement. This database is used to store the configurations for the incident types and categories, and the incident activity trails.NOTE: The settings and incident icons of the Incident Manager role are stored in the Directory database.
-
Click the Properties tab, and configure the general incident
management settings:
- Retention period
- Specify how long you want to keep incidents in the system after they are closed. This value can be individually defined for each incident type.
- Priorities
- You can add custom values to the predefined incident priorities: Low, Medium, High, and Critical. Use the arrow buttons to change the order of the priorities. You cannot rename or delete the predefined priorities. Incidents that have a higher Priority will be queued at the top of the list. Higher priority incidents also auto-open first.
- Profiles
-
- Auto-assign mode
- Enable this option to let the system automatically assign incident management profiles to users when they log on.
- Document management
- You must configure the document location before you can add support documents for
Mission Control.
- Document API port
- Port (default=5090) used by the role to upload and download web documents.
- Export settings
- You can configure the export settings for your incident.
- Branding image
- By default, the incident exports include the Mission Control logo. You can choose one of the
following options to appear on your incident exports:
- None
- No branding logo.
- Genetec Mission Control™ logo
- The default Mission Control logo.
- Custom logo
- Your own logo. You can click the folder icon and choose an image with 256 x 256 pixels or above in size. The image is resized to 300 x 300 pixels with the same aspect ratio.
- Location for exporting incident on close
- Set the folder path to save incidents exported automatically by the system when
they are closed.NOTE: Default folder path: C:\ProgramData\Genetec Security Center <version>\
- Format for exporting incident on close
- Set one of the following file formats for incidents exported automatically by
the system when they are closed:
- PDF (default)
- XML
- HTML
- Trigger incident settings
- Choose one of the following time stamp options for incidents triggered manually in the
Incident monitoring task:
- When incident is triggered
- When you click Trigger in the Trigger incident dialog box (default).
- When manual incident trigger dialog box opens
- When the Trigger incident dialog box opens after you click Trigger incident.
-
NOTE: If you have users logged in to Security Desk, they must log off and log on again for the changes to take effect.
- Additional fields
- You can add additional fields to incident properties. Every additional field you add
can be viewed in the Incident details pane in Security Desk.Mission Control includes the following default data types for additional fields:
- DateTime
- Gregorian calendar date and time.
- Date
- Gregorian calendar date.
- Boolean
- Boolean data, represented by a check box.
- Number
- Real numbers from -100000 to 100000.
- String
- An alphanumeric string.
- URL
- Web page URL that can be configured with dynamic fields pointing to specific pages based on Custom fields, Additional fields or Incident properties.
You can use these additional fields in the following ways:- Enable the system to automatically select a dynamic SOP step option.
- As a parameter in the Conditional activities automation workflow activity.
- As a filter criteria in the Incident report task.
- As an incident list column in the Incident monitoring task.
-
Watch this video to learn more. Click the Captions icon (CC) to turn on video captions in one of the available languages.
- Custom column: Alarm context
- Starting with Mission Control 3.1.1.0, the Alarm context column which displays the context of a triggered alarm in the incident list is displayed by default and does not need additional configuration.
-
Click the RabbitMQ tab, and configure the RabbitMQ
settings:
RabbitMQ is the message broker software used by Mission Control and other Security Center components.
- Username
- Your RabbitMQ web interface logon username.
- Password
- The password for your RabbitMQ web interface logon.
- Servers
-
- RabbitMQ Servers
- The RabbitMQ server runs on your main server by default. If your RabbitMQ server runs on a different server, change it here. If you have set up a RabbitMQ cluster, add the IP address of all your RabbitMQ servers here.
- Port
- By default, RabbitMQ uses port 5671 for SSL communication.
- HTTPS API port
- By default, the web management SSL port is15671.
-
NOTE: If you want to change the default port numbers used by Mission Control, you must either change it during the installation process or change the port in the RabbitMQ.conf file. After modifying the RabbitMQ.conf, you must update the details here to match.
-
NOTE: If RabbitMQ is not installed on the same server as the Incident Manager role, copy the RabbitMQ certificates to the Incident Manager server.
- Failover configuration
-
- Enable failover
- Enable this option to configure the RabbitMQ servers for failover with the Incident Manager server. During the failover, data from incident triggers are lost until the Incident Manager server role is online.
- RabbitMQ server assignment
-
- Incident Manager Servers
- By default, the main server is selected. Select the server which is to be configured for failover.
- RabbitMQ servers
- Select one or multiple RabbitMQ servers that are available to be the failover servers.
- Click the States tab, configure the incident states.
- Click the Events tab, specify the Security Center event types that will be processed by Mission Control.
Results
NOTE:
Although we do our best to keep our videos current, the
information presented in this video might become outdated with each new release. If you
find anything wrong with this video, feel free to contact
us.