Create performance monitoring rules
You can choose what performance items are monitored on a device by defining monitoring rules that specify what the monitoring agent checks on the device. To do this you need to deploy a ruleset to the device that includes a Performance monitoring alert rule.
There are a large number of performance counters that can be monitored. When you create a performance monitor rule you can turn any of these items on or off, specify how frequently to check them, and, for some items, set performance thresholds. You can also select services running on the devices that you want to monitor.
The overall process for creating performance monitoring rules is as follows:
- Include Performance monitoring as a rule in the alert ruleset for the device.
- Deploy the alert ruleset to the device. (You can target multiple devices to deploy the ruleset to multiple devices, but then need to define performance monitoring on individual devices.)
- Create performance monitoring rules on the device using the Real-time inventory and monitoring console. Some events such as services also require that you select each service you want monitored (see detailed steps below).
To select a performance counter to monitor
- Click Tools > Reporting/Monitoring > Health dashboard.
- In list of devices, double-click the device you want to configure.
The Real-time inventory and monitoring console opens in another browser window.
- In the left navigation pane, click Monitoring.
- Click the Performance counter settings tab.
- From the Objects column, select the object you want to monitor.
- From the Instances column, select the instance of the object you want to monitor, if applicable.
- From the Counters column, select the specific counter you want to monitor.
- If the counter you want doesn't appear in the list, click Reload counters to refresh the list with any new objects, instances, or counters.
- Specify the polling frequency (every n seconds) and the number of days to keep the counter history.
- In the Alert after counter is out of range box, specify the number of times the counter will be allowed to cross the thresholds before an alert is generated.
- Specify upper and/or lower thresholds.
- Click Apply.
- Performance log files can quickly grow in size; polling a single counter at a two-second interval adds 2.5 MB of information to the performance log daily.
- A warning alert is generated when a performance counter drops below a lower threshold. When a performance counter exceeds an upper threshold on a Windows device, a critical alert is generated.
- When you set thresholds, remember that alerts will be generated regardless of whether an upper or lower threshold is crossed. In the case of something like disk space, you may want to be alerted only if the device is running low. In this case, you would want to set the upper threshold to a high enough number that you would not be alerted if a lot of disk space became available on the device.
- Changing the Alert after counter is out of range number lets you focus on an issue when it is a persistent problem or when it is an isolated event. For example, if you are monitoring the bytes sent from a Web server, you will receive alerts when the bytes/sec consistently runs high. Or, you can specify a low number such as 1 or 2 to receive an alert whenever your anonymous FTP connections exceed a certain number of users.
- When you edit services in a monitoring rule, the Available services list displays known services from the inventory database. No services are displayed in the Available services list box until an agent has been deployed to one or more devices and an inventory scan is returned to the core.
Generate an XML file for a ruleset
As part of the deployment process, an XML page is created that lists the deployed ruleset and devices the ruleset was deployed to. This report is saved on the core server in the Ldlogon directory, and is named with a sequential number assigned by the database.
If you want to view this XML page separately from deploying a ruleset, click the Generate XML button and then click the link to view the XML file. Generating a ruleset as XML also allows it to be displayed in the list of available rulesets in the Agent configuration settings.
Was this article useful?
The topic was:
Copyright © 2016, LANDESK. All rights reserved.