System takes too long to trigger incidents - Genetec Mission Control™ 2.12.0.0

Genetec Mission Control™ User Guide 2.12.0.0

series
Genetec Mission Control™ 2.12.0.0
revised_modified
2019-07-18
category_custom
Guides
Guides > User guides
prodname_custom
Mission Control > Genetec Mission Control™
vrm_version
2.12

When the system takes too long to trigger incidents, you can resolve the issue by filtering out unnecessary events from the RabbitMQ event queue.

Symptoms

Incidents are not triggered in a timely manner in Genetec Mission Control™.

Cause

Depending on the configuration of the system and its connected entities, the directory role might be sending too many events to the Genetec Mission Control™ RabbitMQ server. This makes the event queue too large to process new events, thereby creating a delay in triggering incidents. You can find details on the number of events in queue and response rate of the RabbitMQ server at https://localhost:15671.

Solution

  1. Stop the Incident Manager role in Config Tool:
    • Go to System > Roles > Incident Manager.
    • Right-click Incident Manager.
    • Select Maintenance > Deactivate role.
  2. Log on to the RabbitMQ service from https://localhost:15671.
  3. Click the Queues tab and then click ExternalEventsQueue.
  4. Click Purge and then click Purge messages to clear the queue.
  5. Activate the Incident Manager role again:
    • Go to System > Roles > Incident Manager.
    • Right-click Incident Manager.
    • Select Maintenance > Activate role.
  6. Filter the events that you do not need in your Genetec Mission Control™ configuration:
    1. In Config Tool, go to System > Roles > Incident Manager.
    2. Click the Events tab.
    3. Deselect the events that you do not need.

    To learn more about event filtering, see Specifying allowed events for Genetec Mission Control™.