Network Management

Alerts are triggering even for disabled sensors in NPM

This article provides example configuration for alerts that are triggered even though the hardware sensor is disabled.

First published date

2/13/2020 8:29 AM

Last published date

10/21/2020 8:39 PM

Overview

On this example Ethernet1/9 and Ethernet 1/10 is already disabled for hardware sensor monitor but still sending alerts for hardware sensor.

Product section

Network Performance Monitor

Cause

All canned alerts have trigger condition defined in the way that sensors with field IsDisabled=Yes are omitted from results. This does the trick. However this works only when you have fresh installation. For upgrades from previous versions of NPM the canned alerts stay untouched, thus also won't receive the updated trigger condition! All such alerts (canned alerts after upgrade or user defined alerts) should be modified and theirs trigger condition adjusted in order to filter out disabled sensors.

Resolution

1. Edit the existing alert and on the triggered condition insert the highlighted condition.

2. The condition will exclude all interfaces that disable hardware sensor and will not trigger an alert for those interfaces.

Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment. You elect to use third-party content at your own risk, and you will be solely responsible for the incorporation of the same if any.