Optimizing Alarms and Events

When correctly configured, the Plixer Scrutinizer Alarm Monitor is capable of reporting information that is accurate, relevant, and uniquely tailored to the organization or team using it.

To achieve this, the following configuration steps related to Alarms and Events should be completed as part of deploying Plixer Scrutinizer.

1. Navigate to the Admin > Settings > Data History tray and adjust the Alarm Retention Days, Alarm Retention Size, and Auto-Acknowledge Alarms values as needed.

2. In the Admin > Settings > Alarm Notifications tray, verify that the Alarm Notifications options are correctly configured.

3. Go to the Admin > Alarm Monitor > Notification Profiles page and create Notification Profiles to enable additional notification channels.

4. Go to the Admin > Alarm Monitor > Alarm Policies page and:

   • Set the status of any Alarm Policies that are unnecessary or irrelevant to the environment to Inactive (must be done as a bulk action after selecting at least one Policy).

   • Set the status of Alarm Policies whose Events should be monitored but not reported in the Alarm Monitor to Store (must be done as bulk action after selecting at least one Policy).

   • Assign the appropriate Notification Profiles to any Alarm Policies that require them.

   Note

   The Timeout and Weight values of an Alarm Policy can be adjusted at a later time, after evaluating reporting behavior for Events under it.

5. Follow the Flow Analytics configuration guide to correctly set up FA-based functions and features.

6. Follow the Plixer ML Engine configuration guide to correctly set up machine-learning-based functions and features.

After the initial setup has been completed, it is highly recommended to continue to evaluate Alarm and Event reporting behavior and make further adjustments to the various elements’ configurations as necessary.