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?
This is Working as designed / Documentation clarification.
NOTE: Not all MCS Profiles create Default Templates
Create the Alarm Policy and related Thresholds Manually for Disk IO Monitor (enhanced)