Management and Security powered by Landesk
Example: Configuring an alert ruleset for disk space problems
The following procedure demonstrates a simple example of the first step in cofiguring a custom alert ruleset. In this example, a single alert rule is added to a ruleset.
- In the core server console, click Configuration > Alerting.
- On the toolbar, click New. Type a name for the ruleset and a description (such as "Disk space 90% full"), and click OK.
- In the Alert rulesets list, click the name of the new ruleset and click Edit on the toolbar.
- In the Ruleset configuration window, click Alerts in the left column.
A tree view of alerts is displayed, with a grid containing alerts and their descriptions. You can click All alerts to view all available alerts, or click a category in the tree to view a specific group of alerts. Depending on your screen resolution, you may want to resize the columns to read items in the lists.
- In the tree view, under the Monitor group, click the Drive space alert.
- In the grid, select Default disk usage, then click Edit in the right column.
- In the Drive space monitoring dialog box, you can set the Polling interval frequency to change how often the drive space usage will be monitored. To change the thresholds at which alerts are triggered, click Drive space and set percentages for warning and critical alerts. (These are percentages of total available drive space that are full.) Click OK to save the settings.
- On the Alerts page, in the right column, click Rules > Add.
Three "wells" are displayed at the bottom of the page. Use these wells to combine alert, action, and time items to create an alert rule.
- Drag the Default disk usage alert to the Alerts well.
- In the left column, click Actions. Click the Standard folder. Drag Log alert to local NT event log to the Actions well.
For every alert rule you create, a default Log handler configuration action is already included in the Actions well. If you want to add other actions, such as sending an e-mail, you need to define an action and then drag it to the Actions well.
- In the left column, click Time. In the Time list, drag Always to the Time well.
- Click OK next to the wells to save the rule, and click OK again at the success message.
You have now created an alert rule that is part of the ruleset. To save your changes, you need to publish the ruleset.
- In the right column, click the Publish button.
You can go back to the Rules summary page to view the rule and, if you want, edit it.
- In the left column, click Rules summary.
Note that there are two rules listed. One is for the rule you created (with a Log alert to local NT event log action), and the other is a default rule that sends the alert notifications to the core server (with a Log handler configuration action). This is automatically created for every rule you define so that all alerts are logged at the core server. You can't delete this rule unless you delete all rules for an alert.
- Select the Default disk usage rule with Log alert to local NT event log as the action, then in the right column click Rules > Edit. Use this dialog box to change settings for the rule.
- To change the action associated with the rule, select a different item from the Action drop-down list.
- To change the time during the which the alert rule is active, select a different item in the Time drop-down list.
- To change the severity levels for alert notifications, click the State icons. A dimmed icon will not be used, so to receive alerts only for critical status alerts, click the Warning (State 2) icon, a yellow triangle, to turn it off.
- Select the Health check box to include disk space usage as an alert that contributes to the device's health status.
- Click OK. You can now see the changes you made reflected in the Rules summary list.
To save the changes to this ruleset, you need to publish it again. It will then be saved and will be available for deployment in your list of rulesets.
- In the right column, click Publish.
When you return to the management console, the new ruleset you created is listed under Alert rulesets.
Was this article useful?
The topic was:
Not what I expected
Copyright © 2017, Ivanti. All rights reserved.