CA Unified Infrastructure Management Probe Guide for Performance Collector
CA Unified Infrastructure Management Probe Guide for Performance Collector v1.8 series Copyright Notice This online help system (the "System") is for your informational purposes only and is subject to change or withdrawal by CA at any time. This System may not be copied, transferred, reproduced, disclosed, modified or duplicated, in whole or in part, without the prior written consent of CA. This System is confidential and proprietary information of CA and protected by the copyright laws of the United States and international treaties. This System may not be disclosed by you or used for any purpose other than as may be permitted in a separate agreement between you and CA governing your use of the CA software to which the System relates (the “CA Software”). Such agreement is not modified in any way by the terms of this notice. Notwithstanding the foregoing, if you are a licensed user of the CA Software you may make one copy of the System for internal use by you and your employees, provided that all CA copyright notices and legends are affixed to the reproduced copy. The right to make a copy of the System is limited to the period during which the license for the CA Software remains in full force and effect. Should the license terminate for any reason, it shall be your responsibility to certify in writing to CA that all copies and partial copies of the System have been destroyed. TO THE EXTENT PERMITTED BY APPLICABLE LAW, CA PROVIDES THIS SYSTEM “AS IS” WITHOUT WARRANTY OF ANY KIND, INCLUDING WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NONINFRINGEMENT. IN NO EVENT WILL CA BE LIABLE TO YOU OR ANY THIRD PARTY FOR ANY LOSS OR DAMAGE, DIRECT OR INDIRECT, FROM THE USE OF THIS SYSTEM, INCLUDING WITHOUT LIMITATION, LOST PROFITS, LOST INVESTMENT, BUSINESS INTERRUPTION, GOODWILL, OR LOST DATA, EVEN IF CA IS EXPRESSLY ADVISED IN ADVANCE OF THE POSSIBILITY OF SUCH LOSS OR DAMAGE. The manufacturer of this System is CA. Provided with “Restricted Rights.” Use, duplication or disclosure by the United States Government is subject to the restrictions set forth in FAR Sections 12.212, 52.227-14, and 52.227-19(c)(1) - (2) and DFARS Section 252.227-7014(b)(3), as applicable, or their successors. Copyright © 2014 CA. All rights reserved. All trademarks, trade names, service marks, and logos referenced herein belong to their respective companies. Legal information on third-party and public domain software used in this product is documented in the Third-Party Licenses and Terms of Use (http://docs.nimsoft.com/prodhelp/en_US/Library/Legal.html). Contact CA Contact CA Support For your convenience, CA Technologies provides one site where you can access the information that you need for your Home Office, Small Business, and Enterprise CA Technologies products. At http://ca.com/support, you can access the following resources: ■ Online and telephone contact information for technical assistance and customer services ■ Information about user communities and forums ■ Product and documentation downloads ■ CA Support policies and guidelines ■ Other helpful resources appropriate for your product Providing Feedback about Product Documentation Send comments or questions about CA Technologies product documentation to [email protected]. To provide feedback about general CA Technologies product documentation, complete our short customer survey which is available on the support website at http://ca.com/docs. Contents Chapter 1: ntperf 1.8 7 ntperf Overview ........................................................................................................................................................... 7 Chapter 2: ntperf Probe Deployment 9 Prerequisites ................................................................................................................................................................ 9 Configure Instances for Performance Object Counter ........................................................................................ 10 Supported Platforms .................................................................................................................................................. 10 System Requirements ................................................................................................................................................ 10 Software Requirements ............................................................................................................................................. 11 Monitoring System Requirements ............................................................................................................................. 11 Probe Deployment Information ................................................................................................................................. 11 Chapter 3: ntperf Configuration 13 Probe Defaults ............................................................................................................................................................ 13 Probe Configuration Interface Installation for ntperf ................................................................................................ 13 Probe Configuration ................................................................................................................................................... 13 Setup Tab ............................................................................................................................................................ 14 Status Tab ............................................................................................................................................................ 15 Messages Tab ...................................................................................................................................................... 25 Chapter 4: QoS Threshold Metrics 29 ntperf QoS Metrics ..................................................................................................................................................... 29 ntperf Alert Metrics Default Settings ......................................................................................................................... 30 Contents 5 Chapter 1: ntperf 1.8 This description applies to ntperf version 1.8x. This section contains the following topics: ntperf Overview (see page 7) Documentation Changes (see page 8) ntperf Overview The Performance Collector probe can monitor performance counters on Windows NT. The probe is configured to send alarms on unexpected values and generate quality of service (QoS) messages.The QoS messages may contain performance values. Chapter 1: ntperf 1.8 7 ntperf Overview Documentation Changes This table describes the version history for this document. Version Date What's New? 1.8 October 2014 Updated the Alarm on Value Tab and Alarm on Value Change Tab topics. 1.8 September 2014 Updated the Object Selection Tab, ntperf QoS Metrics, and added the Configure Instances for Performance Object Counter topic. 1.8 March 2014 Updated Probe Configuration section. 1.8 February 2013 ■ Added Probe Defaults topic. ■ Added support for reading alarm tokens from configuration. ■ Added support for web-based SOC. Related Documentation Documentation for other versions of the ntperf probe The Release Notes for the ntperf probe Monitor Metrics Reference Information for CA Unified Infrastructure Management Probes (http://docs.nimsoft.com/prodhelp/en_US/Probes/ProbeReference/index.htm) 8 Probe Guide for Performance Collector Chapter 2: ntperf Probe Deployment This section contains the prerequisites, system requirements and deployment information for the ntperf probe. This section contains the following topics: Prerequisites (see page 9) Supported Platforms (see page 10) System Requirements (see page 10) Software Requirements (see page 11) Monitoring System Requirements (see page 11) Probe Deployment Information (see page 11) Prerequisites While installing ntperf probe on 64-bit Windows, both the ntperf and ntperf64 probes are installed. The ntperf64 probe is a native 64-bit program that will only read 64-bit objects. For 32-bit performance objects, the ntperf probe should be used. Chapter 2: ntperf Probe Deployment 9 Supported Platforms Configure Instances for Performance Object Counter When you create a monitoring profile, the Object Selection Tab lets you select performance object for monitoring along with their threshold values. When you select an Object and a Counter, there can be instances with similar name. You must add a new key value in your system registry to show instances in the application_pprocessID format. Notes: ■ This registry key impacts only .NET applications being monitored. ■ You require administrator rights on your system to modify the registry. Follow these steps: 1. Open regedit in your system. 2. Navigate to the following registry key: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\.NETFramework\Perfo rmance 3. Right-click in the blank space and select New > DWORD (32-bit) Value. 4. Enter the following parameters for the new value: ■ Value name: ProcessNameFormat ■ Value type: REG_DWORD ■ Value: 1 (0x00000001) Instances for Performance Object Counter are configured. Supported Platforms Refer to the Compatibility Support Matrix for the latest information about supported platforms. See also the Support Matrix for Probes for more specific information about the probe. System Requirements The ntperf probe should be installed on systems with the following minimum resources: ■ Memory: 2-4GB of RAM. Probe's OOB configuration requires 256MB of RAM ■ CPU: 3GHz dual-core processor, 32-bit or 64-bit 10 Probe Guide for Performance Collector Software Requirements Software Requirements The ntperf probe requires the following software environment: ■ Nimsoft Monitor Server 7.1 to 7.6 or CA Unified Infrastructure Management 8.0 or later ■ Robot 5.23 or later ■ Java Virtual Machine 1.6 or later Monitoring System Requirements The ntperf probe monitors selected object/instance/counter values in the performance registry of Windows NT systems. Probe Deployment Information There are three ways to distribute archive packages. You can distribute the package within the web-based Admin Console (for supported probes), from within Infrastructure Manager, or use the standalone Distribution application. See Probe Deployment for more information on deploying probes. Chapter 2: ntperf Probe Deployment 11 Chapter 3: ntperf Configuration This section describes the configuration concepts and procedures for setting up the ntperf probe. This section contains the following topics: Probe Defaults (see page 13) Probe Configuration Interface Installation for ntperf (see page 13) Probe Configuration (see page 13) Probe Defaults At the time of deploying a probe for the first time on robot, some default configuration will get deployed automatically. These probe defaults could be Alarms, QoS, Profiles, and so on which save time to configure the default settings. These probe defaults will be seen on a fresh install, that is no instance of that probe is already available on that robot in activated or deactivated state. Probe Configuration Interface Installation for ntperf The probe configuration interface is automatically downloaded and installed by the Infrastructure Manager when the probe is deployed on a robot. Probe Configuration The ntperf probe is configured by defining one or more profiles, each identifying a particular performance value. You can set a threshold value for this value. When the performance value exceeds this value, the probe will send an alarm. There are three main tabs as listed below: ■ Setup (see page 14) ■ Status (see page 15) ■ Messages (see page 25) Chapter 3: ntperf Configuration 13 Probe Configuration Setup Tab The Setup tab is used to configure some general settings for the probe, which are common for all monitoring profiles. 14 Probe Guide for Performance Collector Probe Configuration The fields displayed in the above dialog are explained below: Check interval Specify the time interval at which the performance values are sampled. Please refer to the description of Alarms on Value (see page 20) tab for more details about sampling. Default message level Specify the default message level for alarm messages. This value can be overridden in each watcher. Configurator request timeout Specify the time out limit to list all performance objects and performance counters on GUI. While adding new profiles (or editing existing ones), sometimes It may take a lot of time to update these lists. Specifying a time out limit you allow the configurator to wait before canceling the request automatically. Log file Specify the file to which the probe logs information about its internal activity and the level of details written to the log file. Log level Specify the depth of details for which the log should be maintained. Log as little as possible during normal operation to minimize disk consumption, and increase the amount of detail when debugging. Status Tab The Status tab displays a list of performance profiles currently configured. Each profile can be activated or deactivated directly with a check box. Chapter 3: ntperf Configuration 15 Probe Configuration Right-clicking in the Performance profiles list gives you the following options: ■ Add profile - create a new performance watcher. ■ Edit profile - edit the currently selected watcher. ■ Remove profile - remove the currently selected watcher. Note: To Add/Edit a performance profile refer the Profile Configuration section (see page 13). Profile Configuration On the Status tab (see page 15) when you right-click and select the Add profile or Edit profile option, the Profile properties dialog is displayed. This dialog is used to configure profile specific parameters. 16 Probe Guide for Performance Collector Probe Configuration The fields displayed in the above dialog are explained below: Name Defines the name of profile. You must give a logical profile name so that it would be easier to remember its configuration details. Active Used to activate or deactivate the profile. Description Defines a brief information about the profile based on the parameters configured to give idea about profile function. Apart from these common fields there are four tabs as listed below: ■ Object Selection (see page 18) ■ Alarm on Value (see page 20) ■ Alarm on Value Change (see page 22) ■ Miscellaneous (see page 24) Chapter 3: ntperf Configuration 17 Probe Configuration Object Selection Tab The Object Selection tab is used to select the performance object to be monitored along with their threshold values. 18 Probe Guide for Performance Collector Probe Configuration The fields displayed in the above dialog are explained below: Object Specify the performance object to monitor. Counter Specify the counter for which the value will be extracted. Instance Specify the instance of the selected counter. When a performance object can have several instances (e.g. Process), the particular instance is identified here. If no value is specified, the watcher will be applied to all instances found. Note: When you select an Object and a Counter, there can be instances with similar name. You must add a new key value in your system registry to show instances in the application_pprocessID format. The registry key value only works for the .NET applications under monitoring. For more information, refer the Configure Instances for Performance Object Counter (see page 10) section. Calculate Value using scaling ratio Select this option if you wish to specify a scaling ratio to calculate the value. Chapter 3: ntperf Configuration 19 Probe Configuration Alarm on Value Tab The Alarm on Value tab is used to set a threshold value. If this threshold value is exceeded, the alarm specified will be issued. 20 Probe Guide for Performance Collector Probe Configuration The fields displayed in the above dialog are explained below: Watch Specifies the threshold parameters for monitoring the counter value and generating alarms. Threshold Operator Specifies the threshold operator (for example, = and <=) for comparing the actual value with the threshold value. Threshold Value Specifies the threshold value for generating alarm. For example, if your threshold operator is <= (less than or equal to), threshold value is 1250, and the monitor value is 1355; then the probe generates an alarm. If the monitor value is below or equal to 1250, no alarm is generated in the given scenario. Fetch Current Fetches the current value of the counter and displays it in the Threshold Value field. Sampling Specifies the number of performance values for which average based on the Check Interval period (specified in the Setup tab (see page 14)) will be computed. For example, if the Sampling value is specified as 5 and the Check Interval is configured to 60 seconds, then average of the latest 5 performance values received during each 60-second period will be computed. Alarm message Specifies the Alarm message to be raised, when the threshold value is breached. It overrides the built-in alarm message definition with your own values. Chapter 3: ntperf Configuration 21 Probe Configuration Alarm on Value Change Tab The Alarm on Value Change tab is used set a threshold for the expected change of the measured value. If this threshold value is exceeded, the alarm is issued. 22 Probe Guide for Performance Collector Probe Configuration The fields displayed in the above dialog are explained below: Watch Specifies the parameter for tracking the change in the counter value. Threshold Operator Specifies the threshold operator (for example, = and <=) for comparing the actual value with the threshold value. Threshold Value Specifies the threshold value for generating alarms. For example, if your threshold operator is <= (less than or equal to), threshold value is 100, and the change in monitor value is 105; then the probe generates an alarm. If the change in monitor value is below or equal to 100, no alarm is generated in the given scenario. Sampling Change summarized over all samples Select this option to make a summary of changes occurred in the counter value. For example, you have configured 3 in the Samples field of the Alarm on Value tab; then probe calculates delta between 3rd and 1st sample values. Change between each sample Select this option to record changes in each sample individually. For example, you have configured 3 in the Samples field of the Alarm on Value tab; then probe calculates delta between 1st and 2nd sample values, and between 3rd and 2nd sample values. Note: If the value in the Samples field under the Alarm on Value tab is set as one, then delta value is always zero. Messages Message Specifies the alarm message to be raised, when changes are beyond the threshold limit. Clear Message Specifies the clear alarm message. Chapter 3: ntperf Configuration 23 Probe Configuration Miscellaneous Tab The Miscellaneous tab is used to define alarm when specified object is not available for monitoring and the QoS message settings. 24 Probe Guide for Performance Collector Probe Configuration The fields in the above dialog are explained below: Not Found message Specifies a message (text, severity level and subsystem) to be issued if the object is not found. Quality of Service message on Enables the value check box(es) for the QoS message(s) you want to send for this profile. Quality of Service options If this option is not checked, the profile name will be used as QoS table name. If enabled, the name of instances found (if any) will be added to the QoS table name, giving a table name on the format <profile name>/<instance name>. QoS Max Value Scaling Select the Calculate Value using scaling ratio option if you wish to specify a scaling ratio to calculate the value. Messages Tab The Messages tab displays a list of currently configured alarm messages for ntperf probe. On the first configuration, this tab displays some default messages, which can be edited by the user. Users can also add their own messages. Right-clicking the Message pool list displays the following options: ■ New Message - Creates a new alarm message. ■ Edit Message - Modifies the currently selected message details. ■ Delete Message - Removes the currently selected message. Chapter 3: ntperf Configuration 25 Probe Configuration Add/Edit Message The ntperf probe maintains a pool of messages for different type of severities like Error Message, Warning Message and so on. You can add new messages to this pool and edit existing message details as required. Follow theses steps: 1. Right click in the Messages pool list, under Messages tab, and select New Message... option. The Message properties dialog appears: 26 Probe Guide for Performance Collector Probe Configuration The fields displayed in above dialog are explained below: Message text Enter the text to be displayed for the message. You can use variables by typing $ and using the variables from the list displayed. Severity Choose a severity level for the alarm from the drop-down list. Message token Choose a token for the message from the drop-down list. Message subsystem A descriptive text name for the subsystem. In the text field, the following variables can be used: $watcher $description $operation $limit $value $object $instance $counter 2. Configure the message parameters as described above. 3. Click OK to close the Message properties dialog. The New message dialog appears. 4. Define appropriate message name and click OK to save new alarm the message. The New message dialog do not appears, while editing an existing message. Once saved, the alarm is displayed in the message pool list of Messages tab. Note: To edit existing alarm details you have to select the Edit Message... option, rest of the process remains same.However, you cannot edit the message name and it appears in the title of Message Properties dialog. Chapter 3: ntperf Configuration 27 Chapter 4: QoS Threshold Metrics CA Nimsoft Monitor probes contain default QoS threshold values set. The default threshold values provide an idea of the type of values to be entered in the fields. However, the default values are not necessarily recommended best practice values. To aid in tuning thresholds and reducing false-positive alarms, this section describes the QoS metrics and provides the default QoS thresholds. This section contains the following topics: ntperf QoS Metrics (see page 29) ntperf Alert Metrics Default Settings (see page 30) ntperf QoS Metrics The following table describes the checkpoint metrics that can be configured using the ntperf probe. Monitor Name Units Description QOS_WIN_PERF Value Displays the performance data of an operating system, an application, service, or driver. QOS_WIN_PERF_DELTA Value Displays the difference in the incoming performance data over the specified number of samples. QOS_WIN_PERF_DELTA_DAY Value Displays the difference in the incoming performance data over the specified number of samples during a day. QOS_WIN_PERF_DELTA_HOUR Value Displays the difference in the incoming performance data over the specified number of samples during an hour. QOS_WIN_PERF_MAX Value Displays the largest value over the specified time period. Chapter 4: QoS Threshold Metrics 29 ntperf Alert Metrics Default Settings ntperf Alert Metrics Default Settings This section contains the alert metric default settings for the Performance Collector probe. QoS Metric Warning Threshold Warning Severity Error Threshold Error Severity Description AlarmOnDelta - - - critical Difference in monitored value at two intervals exceeds the threshold value. AlarmOnValue - - - critical Specified monitored value exceeds the threshold value. ClearOnDelta - - - clear Difference in monitored value at two intervals is within the threshold. ClearOnValue - - - clear Specified value is within the threshold. - critical No event found. NoFound - 30 Probe Guide for Performance Collector -
© Copyright 2025