N-central Help

Create a rule

Add a new rule to automate device maintenance in SolarWinds N-central. Rules work in conjunction with filters to perform immediate and scheduled tasks.

This procedure can only be performed at the Service Organization level or Customer level.

  1. Click Configuration > MonitoringRules.
  2. Click Add.
  3. To create a new Rule based on the properties of an existing Rule, click Clone.

  4. Select the type of access to be allowed for the rule from one of the following:
    • Public Rules: A public rule can be viewed and edited by the account that created it and any account with a greater permission level. As an Admin, you can edit all the details of any public rule you create. For public rules created by other accounts, you can edit the dashboards on which the rules associate and disassociate notification profile-triggers, add and remove devices and probes. Public rules can be deleted only by the account that created them and permission levels above the customer level.
    • Private Rules: The account that created a private rule view, edit, and delete it, and any account with a greater permission level. Admin accounts cannot view each others private rules.
  5. Click the Devices to Target tab and select the filter that groups the devices you want for the rule.
  6. Click the Network Device Configuration Options tab to create a rule to install SolarWinds N-central features if needed.
  7. Click the Scheduled Tasks Profiles tab and select the automated task the rule will run on the selected devices.
  8. Click the Monitoring Options tab and select the notification profile to send a notification to specific users.
  9. Click the Grant Customers & Sites Access tab to select how to propagate the rule to other customers and sites.
  10. Click Save.

The rule is active immediately. The filters selected are applied. SolarWinds N-central applies the rule to any devices identified by the filter.

There are a number of other events that will trigger a rule:

  • Device import
  • Asset information update provided the filter is attached to at least one of asset info that was changed
  • The first agent install on an existing device
  • Enabling or disabling any features on a device
  • Changing the license mode on the device
  • Updating the rule, nor including changing the rule name)
  • Associating the rule to a new customer, for that customer only
  • Updating any primary property on the device such as the device class, OS, and so on.