MCS disk IO CDM template not creating default Alarm policy
search cancel

MCS disk IO CDM template not creating default Alarm policy

book

Article ID: 432990

calendar_today

Updated On:

Products

DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

In MCS the Disk IO Monitor (enhanced) template successfully deploys configurations to the cdm probe but fails to automatically generate a "Default Alarm Policy" in the Operator Console UI, unlike CPU or Memory templates.

Is there an issue? Is this expected? 

Why no Default Alarm Policy is created for  Disk IO Monitor?

Environment

  • DX UIM 23.4.*
  • CDM any version
  • cdm MCS template 7.22 

 

Cause

This is Working as designed / Documentation clarification. 

  • What causes it?
    Zero-Value Defaults: The template XML defines all threshold values as 0. MCS interprets a zero threshold for throughput/latency as a "Disabled" state, thus suppressing policy generation.

  • Why is it set like this?
    Passive Design: Unlike CPU templates which have pre-defined "Best Practice" thresholds (e.g., 90%), Disk IO metrics are hardware-dependent. The template is intentionally shipped without active default thresholds.


NOTE: Not all MCS Profiles create Default Templates

Resolution

Create the Alarm Policy and related Thresholds Manually for Disk IO Monitor (enhanced)