Hide this message
Looking to compare latest NPM features with previous versions of NPM?
The NPM new feature summary offers a comparison of new features and improvements offered with this release.
Use the reset condition to define what must occur to remove an alert instance from the active alerts list. For example, the "Email me when a Node goes down" alert automatically resets when the node comes back up. You can use the built-in reset conditions or create your own.
When reset conditions are met, the alert is removed from Active Alerts. You can also add actions that occur when the reset conditions are met.
For example, you can create an alert that triggers when nodes in your lab go down. If node
192.168.4.32 goes down, the alert fires for that specific instance of the trigger condition and any escalation levels you create continue until you reset the alert. After the alert is reset, all trigger actions stop and a new alert fires the next time node
192.168.4.32 goes down. If you have created reset actions, the reset actions fire.
When the alert is reset, escalation actions are halted.
Select one of the following reset conditions:
Reset this alert when trigger condition is no longer true (Recommended)
SolarWinds recommends using this reset condition. If the trigger condition is no longer true when the objects are next polled, this selection automatically resets the alert.
You can use the Condition must exist for more than option in the trigger conditions in conjunction with this reset condition. Trigger conditions that involve volatile components, such as high CPU utilization, can trigger excessively with this reset condition.
Reset this alert automatically after
Select to reset an alert after a set amount of time has passed. If this interval is less than the amount of time you wait for different escalation levels, the escalation levels that occur after this interval do not fire. This reset condition is especially useful to remove event-based alerts from Active Alerts.
For example, if the trigger conditions still exists after 48 hours, you can use this to trigger your alert actions again. The alert is reset and triggers as soon as the trigger condition is detected, which is as soon as the objects are polled for this example.
No reset condition - Trigger this alert each time the trigger condition is met
The alert fires each time the trigger conditions are met.
For example, when the alert for node
192.168.4.32 going down fires, a new alert for
192.168.4.32 fires every time the node is down when it is polled.
No reset action
The alert is active and is never reset. To re-trigger the alert, the alert must be manually cleared from the Active Alerts view.
Create a special reset condition for this alert
Select to build a specific reset condition. For example, you can choose to reset the condition when the node has been up for more than 10 minutes.
The alert wizard evaluates the reset condition for errors. If there are no errors, you can proceed to the next step, or go back to previous steps.
See Define the conditions that must exist to trigger an alert or Build complex conditions for more information on creating conditions.
Click Next to schedule when you want the alert to monitor your environment.