Performance threshold monitoring and monitoring for applications such as Exchange, Internet Information Services (IIS), and so on, require packages, called Log Enablement Packages (LEPs), that you can access from the Log Enablement Packages list page.
In the Log Enablement Packages list page, Quest publishes a base set of Windows Reliability and Performance Monitor (PerfMon) templates and non-Windows open-source Perl scripts, so that users can extend their monitoring capability and identify system and application performance issues. These templates and scripts are available so that users do not have to create them from scratch. Monitoring on the appliance works without these additional templates and scripts, but the profiles that are created from the templates and scripts are helpful if you want to do performance threshold monitoring.
ITNinja is a product-agnostic IT collaborative community that serves as a destination for IT professionals to share with one another, and acts as a go-to resource for information on setup and deployment topics. You can browse and contribute to specific software title topics, and other topics, such as deployment, management, configuration, and troubleshooting. The server monitoring community is located at http://itninja.com/community/k1000-monitoring.
In ITNinja, you can find PerfMon templates beyond the standard ones available on the Log Enablement Packages list page.
1. |
a. |
Log in to the appliance Administrator Console, https://appliance_hostname/admin. Or, if the Show organization menu in admin header option is enabled in the appliance General Settings, select an organization in the drop-down list in the top-right corner of the page next to the login information. |
b. |
2. |
Select the check box for the package or packages that you want to install on devices, and select Choose Action > Add to Devices to display the Log Enablement Packages Install page. |
a. |
Click in the Devices text box to display a list of devices within inventory that are compatible with the packages listed in Selected Packages to the right. |
4. |
Optional: For Windows packages, clear the check box for Add Windows OS and Application LEP Profile if that profile is already bound to the device or devices and you do not want to reinstall it. |
◦ |
Leave Replace it selected if you want the current package reinstalled over an existing version. |
◦ |
Select Skip it if you want to retain the package that might be currently installed on the device. For instance, you might have made edits to the package earlier and do not want to lose those changes. |
6. |
7. |
Optional: View the progress of the installation. |
a. |
Click Devices in the Monitoring section of the left navigation bar, and select the name of the monitored device to display its Monitoring Detail page. |
b. |
You can add, remove, and configure performance counters in a monitoring LEP installed on a server.
The Log Enablement Package has been installed on the device. See Install one or more LEPs on monitored devices.
1. |
On the device you want to monitor, start the Performance Monitor, expand the Data Collector Set folder, then expand the User Defined folder. |
3. |
4. |
In the right pane, right-click the DataCollector and select Properties to display the Properties dialog. |
5. |
The Alerts tab enables you to edit the threshold attribute and interval attribute of a performance counter. You can also add and remove counters using this tab. To configure the performance counter:
To add a performance counter to this LEP:
Performance counters for applications installed locally appear in Available counters. You can also select objects and counters from a remote system if you use the list in Select counters from computer or use Browse.
To remove a performance counter from this LEP:
| |||||||||||||||||||||
The objective of the package is to have events logged in the event log so that the monitoring capability of the appliance can pick up an alert, so the check box for Log an entry in the application event log should remain selected. | |||||||||||||||||||||
If you want to set a task to run when the alert is triggered, you define that task on this tab. |
6. |
7. |
© ALL RIGHTS RESERVED. Feedback Términos de uso Privacidad Cookie Preference Center