sqlserver / mysql MCS profiles Default Alarm policies
search cancel

sqlserver / mysql MCS profiles Default Alarm policies

book

Article ID: 419593

calendar_today

Updated On:

Products

DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

What is the expected behavior of Default Policies created by sqlserver and mysql (enhanced) MCS profiles?

When I create an SQLserver MCS profile a default policy is deployed with 68 conditions in it, enabled, no matter of what metrics are enabled in the profile. Is this expected? 

Environment

  • DX UIM 23.4.*
  • sqlserver 6.0*
  • sqlserver_mcs_templates 6.*

 

Cause

Working as Desgined

Resolution

This is the expected behavior. Below is some additional details: 

  • When a profile is created, a default alarm policy is automatically created for all metrics (all checkpoints in the sqlserver). However, alarms are generated only for the metrics that are enabled and have breached their threshold values.

  • If you need that all future default alarm policies to be created in a disabled state, you can update the global setting in the mon_config_service probe's raw configuration by setting the key default_policy_enabled=false under the timed section.

  • To avoid creating default alarm policies altogether, set the key enable_creation_of_default_policy=false under the timed section.
    Note: Existing policies will not be affected by these changes.