Missing alerts due to additional validation for configured ignore_mnt params as this blocks the check from running correctly.DescriptionImpact after ACC-M itom-monitoring-3.1.0 plugin update :Agents began downloading the updated plugin (expected behavior after a plugin upgrade) Following the upgrade, the disk monitoring check began failing because of invalid ignore_mnt values configured in the policy. The disk check logic validates the ignore_mnt mount points: If the referenced disk exists, it will be ignored from monitoring.If the referenced disk does not exist on the server, the check throws an error and fails. Because of this validation failure: Disk monitoring checks did not complete successfullyNo disk threshold events were generatedNo alerts were triggered Steps to Reproduce 1.Configure a os.windows.check-system-disk check with the ignore_mnt parameter. 2. Ensure the configured mount point does not exist on the target server. 3.Deploy the policy via MID Server agents. 4.When the disk monitoring check runs: The plugin validates the disk/mount configuration.Since the disk does not exist, the check fails. 5.The system generates an error event with the message: Provide correct values of include_device, given values doesn't exist 6.Disk threshold events and alerts are not generated.WorkaroundServiceNow recommended isolating the ignore_mnt configuration so it only applies to servers where the mount point exists. Resolution steps implemented: Remove the ignore_mnt parameter from the parent/global monitoring policy.Create a child policy targeting only servers where the mount point is present.Configure the ignore_mnt parameter only in this child policy.Apply the child policy to the relevant servers.Related Problem: PRB1997688