Skip to Content

Setting restart detection

BMC AMI Ops Insightincludes automatic detection of restarts on Db2 subsystems. When the product detects a restart on one of the monitored Db2 subsystems it temporarily suspends scoring for certain KPI groups to avoid sending notifications for false positives that are generated by the restart.

Related topic

Administering

image-2023-6-27_11-45-45.png

You can set the maximum duration for which scoring is suspended for KPI Groups. If the KPI Groups stabilize before reaching this limit, scoring resumes automatically. In case a restart is detected and you still want the product to continue scoring for the Db2 subsystem, you can manually release the subsystem.

If you click on the KPI Groups description, a list of the KPI Groups that are affected by a restart is displayed.

To set the exclusion time

  1. Click the Administration icon Gear Icon.PNG in the title bar. 
  2. Click Scoring Preferences > Restart Detection in the menu on the left side.
  3. Next to Maximum Exclusion Time, click Edit.

  4. Select one of the following options:

    4 Hours

    Default value

    Custom

    Any number of hours and minutes up to 168 hours

    168 Hours

    Maximum value

    Disable

    Disables the maximum exclusion time If you select this option, scoring for the KPIs is suspended until they stabilize, regardless of the amount of time required.

  5. Click Submit.
Warning

Important

When a restart is detected affected KPI Groups appear in the KPI Group Status tab with the restart icon Restart_Icon.png

To release a Db2 subsystem

On the row of the Db2 subsystem you want to release, click the trash icon in the Action.

The Db2 subsystem is released and scoring resumes as normal.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC AMI Ops Insight 3.0