ServerStats lets you monitor a variety of server-side application, database, system, and Web server statistics. You can configure ServerStats to display real-time performance statistics for the various hosts and services available from the server, such as percentage of CPU usage, memory usage, Web server statistics, etc.
The ServerStats configurations contain one or more configured monitors for monitoring performance of application infrastructure during a load test. Once saved, you can add monitors into the configuration and apply them to the system to be monitored.
The Metric Profiles and Metrics options on the ServerStats menu are used to create generic metric profiles and metrics that can be saved for use in multiple configurations. These generic definitions are available when you add a monitor to the configuration. Metric definitions monitor individual data points. Metric profiles monitor a group of data points.
Metric Profiles and Metrics are shipped with a default set of metrics. Additional metrics not included in the default metrics can be accessed by creating custom profiles or metrics.
Oracle Load Testing supports the following metric profiles:
Systems
WebServers
Refer to Appendix B for a description of the metrics included with each profile.
Remote data collectors can be configured to run ServerStats monitors from remote locations.
This chapter describes how to use configuration files, add servers and systems as data sources, and select the counters to monitor.
To create a ServerStats monitor, the following broad tasks must be completed:
Configure the systems you want to monitor and the data collectors you are using either in the System Editor or directly from the ServerStats configuration.
Create generic metric profiles and metrics if you want to use them in more than one configuration, otherwise metric profiles and metrics can be added directly from the configuration.
Create and save a configuration.
Add monitors to the configuration.
Refer to Appendix A for examples.
ServerStats lets you maintain multiple configurations of servers, systems, and counters in different configuration files that can be selected on the Setup Autopilot tab to be run with a load test. Configuration files store a particular set of ServerStats settings for monitoring server performance under load. The files store the following:
Configured data sources
Selected counters from each data source
Selected metric profiles and metrics
Data source and counter properties
Configurations are listed in the ServerStats Configuration section of the Set Up Autopilot tab.
Note:
ServerStats configurations are only initiated and run as part of a load test. If you need to add additional metrics during a load test, start a new session and compare data later using absolute time on the reports.To create a new configuration file:
Select Configurations from the ServerStats menu to open the Configurations options.
New - displays the Add Configuration dialog box.
Edit - displays Edit Configuration dialog box.
Delete - deletes the selected configuration.
Test - tests the selected configuration.
<configurations list> - lists the defined configurations.
Name - displays the name of the selected configuration.
Description - displays the selected configuration's description.
Monitors - lists the metrics included in this configuration.
New - displays the Add Monitor: Step 1 dialog box for adding a new monitor to the configuration.
Edit - displays the Edit Monitor dialog box.
Delete - deletes the selected metric.
<monitors list> - lists the metrics for the configuration.
Click New to open the Add New Configuration dialog box.
Name - displays the name of the configuration. A configuration must be saved before you can add monitors.
Description - displays the configuration description.
Enter a name and description for the configuration.
Click Save.
Click New to display the Add Monitor Step 1 of 3 dialog box. You can add the following types of monitors as described later in this chapter:
Data Source Monitors
Metric Profile Monitors
Metric Monitors
Once you add the monitor and click Finish, the Configurations dialog box is displayed. Click Test to make sure the monitors are configured correctly. Oracle Load Testing tries to start the monitors and collect data from the systems the monitors are configured against.
Click Close to exit the Configurations dialog box.
To edit a configuration:
Select Configurations from the ServerStats menu to open the Configurations options.
Select the configuration you want to change.
Click Edit above the list of configurations to display the Edit Configuration dialog box for changing the name and description of the configuration.
Name - displays the name of the configuration.
Description - displays the configuration description.
Click New in the Monitors pane to add a dedicated monitor, metric monitor, or metric profile monitor.
Click on an existing monitor and click Edit to display the Edit Monitor dialog box where you can change the server location, collection interval, or other properties associated with this monitor.
Click on an existing monitor and click Delete to remove the monitor from the configuration.
Click Test to make sure the monitor works. Oracle Load Testing tries to start the monitor and collect data from the system the monitor is configured against.
Click Close to exit the Configurations dialog box.
You can add the following data source monitors:
COM+ - The ComPlus Monitor retrieves data for counters provided by ComPlus objects on Windows 2000 or later operating systems. The counters that are available are determined by the ComPlus applications that are installed on your system.
Database - You can set up a monitor that performs a database query for an individual machine.
Enterprise Manager - You can set up which Enterprise Manager metrics to view during or after a load session to drill down in Enterprise Manager from Oracle Load Testing. This data source configuration specifies the data used to create a URL request to Enterprise Manager for accessing Weblogic Domain Metrics, Weblogic JVM Metrics or Oracle databases.
IBM WebSphere PMI - WebSphere PMI is an easy way to confirm that a host is responding.
JMX - The JMX monitor lets you determine if a Java application is performing properly. The JMX monitor checks the specified JMX MBean Attribute values to confirm that the Java application is performing as expected. The JMX monitor also provides an easy way to confirm whether or not the JMX application is running.
Perfmon - A Perfmon monitor checks on the performance of a specific Perfmon metric on a single machine. The monitor must have appropriate privileges to access the Perfmon statistics on the monitored machine.
Ping - Ping is an easy way to confirm that a host is responding The Ping monitor sends an echo request to a specified host and waits for a reply. The monitor returns the round trip time.
SNMP - An SNMP (Simple Network Management Protocol) monitor provides specific performance and configuration information on network devices, such as routers, or hosts, such as workstations or mainframes. To use this monitor, enable SNMP on the machine you intend to monitor. Also, be sure that the MIB data you plan on collecting is supported by the SNMP daemon on the monitored machine.
URL - A URL monitor lets you determine if a URL that is critical to your web site is functioning as it should. In addition, the URL monitor can be used to parse data from the Apache server status page using a regular expression.
Virtual Agent - You can set up Virtual Agent monitors to run an executable program from the command line of the system. You specify a Perl expression to return metrics from the command. Virtual Agent is an easy way to execute operating system or custom programs on a host and return specific metrics. The Virtual Agent used to be called Remote Agent.
Refer to Appendix B for examples.
To monitor disk performance on a Windows machine, Diskperf -yv must be enabled on that machine. See "Using Diskperf" later in this chapter for more information.
Select Configurations from the ServerStats menu to open the Configurations options.
Select the configuration to which you want to add a dedicated monitor and click New in the Monitors pane to display the Add Monitor Step 1 dialog box.
This dialog box is where you select the type of monitor you want to add. Expand the appropriate node and select the data source, metric, or metric profile that you want to add.
Expand the Data Sources node, select the data source for the type of monitor you want to add and click Next. The Add Monitor Step 2 dialog box is displayed.
Monitor
Monitored System - Displays information about the monitored system.
Name - enter or select the system to sample. Oracle Load Testing Server is the system on which Oracle Load Testing is installed.
Host Name or IP - displays the host name or IP address of the selected system.
Add - displays the Add Monitored System dialog box for specifying a new system to monitor.
Edit - displays the Edit Monitored System dialog box for editing the selected system.
Monitored System Details - displays details about the monitored system. The information displayed is based on the type of data source being used.
Note:
Data Collector is not used with the Enterprise Manager data source. This section does not appear for Enterprise Manager monitors.Name - enter or select the data collector to use for sampling the system.
Host Name or IP - displays the host name or IP address of the selected system.
Add - displays the Add Data Collector dialog box for specifying a new data collector.
Edit - displays the Edit Data Collector dialog box for editing the selected data collector.
Enter the Monitored System and Data Collector or click the down arrow to select from a list.
Enter the collection interval.
IBM WebSphere PMI requires additional information for discovery. Enter this data and click Next. The Add Monitor Step 3 dialog box is displayed.
This dialog box has different fields based on the type of data source selected. Refer to the following sections for a description of each.
Note:
Counter discovery can be memory intensive. You may need to increase the memory available to the server if discovery is not successful. Refer to "Setting the Server Memory Size" later in this chapter.For monitors that require them, enter a name for the monitor. and the monitor properties. These fields differ depending on the type of monitor. For those monitors for which discovery was performed, select the metrics you want to use and click Add.
Click Finish.
The Configurations dialog box is displayed. Click Test to make sure the monitor is configured correctly.
Click Close to exit the Configurations dialog box.
This section describes the additional fields required for the COM+ data source monitor.
Monitor
Select Counters - select the counters you want to use and click Add.
Add - adds the selected counters to the Counters list.
Counters - displays the selected counters.
This section describes the additional fields required for the Database data source monitor.
Name - enter a name for the monitor.
Type - displays the type of monitor you are adding.
Query - Enter a valid database statement. For example, you can enter the following Oracle SELECT statement:
select value from v$sysstat where statistic# = 1
If your database server supports returning a result set from a stored procedure you can call the procedure. For example, the following SQL Server stored procedure, present in the database, returns a result set (not an output parameter) showing the configured sample rate (samples/minute):
p_computeSampleRate
Report Type
Measure Query Time - Select this option to see how long the query takes.
Read Result Set - Select this option to match a value in the result.
Result Pattern - Enter the Perl expression for the value that should be returned for the specified query.
Sample Multiplier - enter the multiplier you want to be applied to the data that is collected. Setting the sample multiplier to 1 means that the data will be reported as is. If the metric measurement is expressed in kilobytes, setting the sample multiplier to 1024 translates it to bytes. If the metric measurement is expressed in milliseconds, setting the sample multiplier to .001 translates it to seconds.
Translation Type - Translation Type controls how a metric's data is displayed in Reports.
No Translation - data is displayed as it is provided by the metric's data source.
Rate (minutes) - data is presented as a number, per minute. For example, if the time interval between two samples was 10 minutes, and 50 errors were found, the Rate (minutes) would be five (5) errors per minute.
Note:
Rate (minutes) translates data sources that return their values as an endlessly increasing counter. If the data source does not return data this way, use No Translation.This section describes the additional fields required for the Enterprise Manager data source monitor.
Monitor
Monitor Properties
Metric type - (required) select a metric type.
Weblogic Domain Metrics - this type queries for Enterprise Manager Weblogic Domain Metrics by adding the weblogic_domain query string parameter to the base Enterprise Manager URL specified in the Enterprise Manager data source in Oracle Load Testing Monitored Systems.
Weblogic JVM Metrics - this type queries for Enterprise Manager Weblogic JVM Metrics by adding the weblogic_j2eeserver query string parameter to the base Enterprise Manager URL specified in the Enterprise Manager data source in Oracle Load Testing Monitored Systems.
Oracle Database Metrics - this type uses the Target to point to a specific database instance as a parameter to the base Enterprise Manager URL specified in the Enterprise Manager data source in Oracle Load Testing Monitored Systems. The URL links to the Enterprise Manager Database Historical Performance page.
Target - (required) specifies the WebLogic domain, JVM, or database from which to gather metrics. For WebLogic domain or JVM, log into the Enterprise Manager instance and select the Targets tab, then select Middleware. Copy the Name string from the Enterprise Manager Middleware page to this field to specify the target. For Oracle Database Metrics, enter the instance of the database you wish to view.
Method Name - (optional) specifies the Java method name string of a specific Java method into which to drill down. The available Method Names are dependent upon the target specified in the Enterprise Manager instance. Method names will need to provided by the Enterprise Manager instance administrator. If specified, the methodName parameter is added to the base Enterprise Manager URL specified in the Enterprise Manager data source in Oracle Load Testing Monitored Systems. If omitted, the main page for the specified type of metric is shown.
Request Name - (optional) specifies the named HTTP request string of a specific request to which to drill down. The available Request Names are dependent upon the target specified in the Enterprise Manager instance. Request names will need to provided by the Enterprise Manager instance administrator. If specified, the requestName parameter is added to the base Enterprise Manager URL specified in the Enterprise Manager data source in Oracle Load Testing Monitored Systems. If omitted, the main page for the specified type of metric is shown.
This section describes the additional fields required for the IBM WebSphere PMI data source monitor.
Monitor
Select Counters - select the counters you want to use and click Add.
Add - adds the selected counters to the Counters list.
This section describes the additional fields required for the JMX data source monitor.
Monitor
Select Counters - select the counters you want to use and click Add.
Add - adds the selected counters to the Counters list.
This section describes the additional fields required for the Perfmon (Windows Performance Monitor) data source monitor.
Performance object - select the object that you want to monitor.
All counters - selects all counters for the selected performance object. Click Add to add them to the Counters list.
Select counters from list - lets you select the counters you want to add for the selected performance object. Select the counter and click Add to add them to the Counters list.
All instances - selects all instances of the selected counter. Click Add to add them to the Counters list.
Select instance from list - lets you select the instances you want to add for the selected counter. Select the instance and click Add to add them to the Counters list.
Add - adds the selected counter to the Counters list.
Counters - lists the counters that will be included in the monitor.
This section describes the additional fields required for the Ping data source monitor.
Name - enter a name for the monitor.
Type - displays the type of monitor you are adding.
Measurement - Specifies the metric to use for the Ping monitor. Select the metric to use: Average Round Trip Time (PingAvgRTT) or Percentage of Success (PingPercentSuccess).
Length - Specifies how many bytes should be included in each echo request packet.
Time to Live - Specifies the maximum number of router hops permitted. If the echo request takes more than the maximum number of hops, it is thrown away and the Ping attempt is treated as a failure.
Sample Multiplier - enter the multiplier you want to be applied to the data that is collected. Setting the sample multiplier to 1 means that the data will be reported as is. If the metric measurement is expressed in kilobytes, setting the sample multiplier to 1024 translates it to bytes. If the metric measurement is expressed in milliseconds, setting the sample multiplier to .001 translates it to seconds.
Translation Type - Translation Type controls how a metric's data is displayed in Reports.
No Translation - data is displayed as it is provided by the metric's data source.
Rate (minutes) - data is presented as a number, per minute. For example, if the time interval between two samples was 10 minutes, and 50 errors were found, the Rate (minutes) would be five (5) errors per minute.
Note:
Rate (minutes) translates data sources that return their values as an endlessly increasing counter. If the data source does not return data this way, use No Translation.This section describes the additional fields required for the SNMP data source monitor.
Monitor
Validate against target machine - when selected, the counters in the selected MIB files are validated against the target machine to verify the machine and data source are available, the login credentials are correct, and the monitor can connect to the counter.
MIB File - select the MIB file containing the OID that you want to monitor.
Upload File - opens a dialog box for selecting the MIB file to upload.
OID list - lists the OIDs in the selected MIB file. Select the OIDs you want to use and click Add.
Add - adds the selected counters to the Counters list.
This section describes the additional fields required for the URL data source monitor.
Name - enter a name for the monitor.
Type - displays the type of monitor you are adding.
URL Usage - specifies whether to use the URL specified in the System Homepage field on the Add/Edit Monitored System dialog box.
Use System Homepage - use the URL specified in the System Homepage field on the Add/Edit Monitored System dialog box.
Specify - enables the URL field for specifying the URL of the page you want to monitor.
URL - Type the URL for the web page you want to check. The URL must be specified with the full protocol designation of http or https. For example: http://www.company.com.
If you use Get as the HTTP Method (the default), simply include any additional parameters you want to include as part of the URL string, for example:
http://search.yahoo.com/bin/search?p=electronics
POST - the Post method, usually associated with a form, allows a much larger amount of information to be associated with the request.
GET - include any additional query strings as part of the URL address.
Note:
Some servers limit the length of URL and query strings to about 240 characters.Post Data - If you select Post as the URL Method, you can add a series of name-value pairs. For example, a URL generated after completing a form may appear as follows:
POST http://www.company.com/cgi-bin/guestbook.pl ...(additional headers) name=Harold&nickname=Harry
To reference this page, enter name=Harold&nickname=Harry in this field.
User Agent - you can specify a particular user agent when you monitor a URL. When you configure a User Agent, the browser and operating system you specify is added to the header of the URL request. This allows you to test pages designed for a specific browser URL confirm that a page designed for multiple browsers works appropriately for each of them.
False - select this option if you want the URL test to prevent the use of cookies when accessing the page.
True - select this option if you want to allow the URL monitor to support cookies as part of the URL request. A fresh cookie is retrieved each time the test is run.
Custom Cookie - type in a cookie value for the page you are monitoring. If you supply a particular value, remember that the cookie is saved and can become out of date. Refresh cookie requests are ignored.
Include image download times - calculates the URL availability and access time with retrieval of embedded images (such as .gif and .jpeg files and references within <img> tags).
Include object download times - calculates URL availability and access time with retrieval of embedded objects (such as ActiveX objects and Java applets). Oracle Load Testing measures the time taken to retrieve data used by objects, but does not include the time needed to retrieve any executable file required in order to interpret the data. Content types other than HTML and images are also classified as objects.
Result of Perl Expression - enter the Perl expression to use if you have selected Result of Perl Expression as the metric type. For example, you could use the following Perl expression to extract requests per second from the Apache Server status page:
/([0-9]+\.[0-9]) requests\/sec/
Username - if the URL specified requires a name and password for access, enter the name in this field.
Password - if the URL specified requires a name and password for access, enter the password in this field.
Use HTTP Proxy - select True if your network makes use of a proxy server.
Proxy Host - specify the name or IP address of the proxy server.
Proxy Port - the port of the proxy server.
Proxy Username - the proxy server login user name.
Proxy Password - the proxy server login password.
Sample Multiplier - enter the multiplier you want to be applied to the data that is collected. Setting the sample multiplier to 1 means that the data will be reported as is. If the metric measurement is expressed in kilobytes, setting the sample multiplier to 1024 translates it to bytes. If the metric measurement is expressed in milliseconds, setting the sample multiplier to .001 translates it to seconds.
Translation Type - Translation Type controls how a metric's data is displayed in Reports.
No Translation - data is displayed as it is provided by the metric's data source.
Rate (minutes) - data is presented as a number, per minute. For example, if the time interval between two samples was 10 minutes, and 50 errors were found, the Rate (minutes) would be five (5) errors per minute.
Note:
Rate (minutes) translates data sources that return their values as an endlessly increasing counter. If the data source does not return data this way, use No Translation.This section describes the additional fields required for the Virtual Agent data source monitor.
Name - enter a name for the monitor.
Type - displays the type of monitor you are adding.
Description - enter a description of the virtual agent monitor.
Command Line - specifies the command to execute on the host machine.
Matching Regexp - specifies a Perl expression to use to report the data returned from the executable program.
Key of value in Regexp - specify the key of value.
Instance Name - specify the instance name.
Sample Multiplier - enter the multiplier you want to be applied to the data that is collected. Setting the sample multiplier to 1 means that the data will be reported as is. If the metric measurement is expressed in kilobytes, setting the sample multiplier to 1024 translates it to bytes. If the metric measurement is expressed in milliseconds, setting the sample multiplier to .001 translates it to seconds.
Translation Type - Translation Type controls how a metric's data is displayed in Reports.
No Translation - data is displayed as it is provided by the metric's data source.
Rate (minutes) - data is presented as a number, per minute. For example, if the time interval between two samples was 10 minutes, and 50 errors were found, the Rate (minutes) would be five (5) errors per minute.
Note:
Rate (minutes) translates data sources that return their values as an endlessly increasing counter. If the data source does not return data this way, use No Translation.You many need to increase the server memory size for the Oracle Load Testing server if discovery fails. To change the server memory size:
Stop the Server.
In the <installdir>\agentmanager\bin\AgentManagerService.conf file, edit the wrapper.java.maxmemory value to be at least 384.
Save the file.
Restart the server.
Metric profiles are collections of metric definitions for monitoring general system types such as WebSphere, Oracle, etc. A profile can then be used to monitor a specific server when it is added to a ServerStats configuration.
Select Configurations from the ServerStats menu.
Select the configuration to which you want to add a Metric Profile monitor and click New in the Monitors pane to display the Add Monitor Step 1 dialog box.
This dialog box is where you select the type of monitor you want to add. Expand the appropriate node and select the data source, metric, or metric profile that you want to add.
Expand the Metric Profiles node, select the type of monitor you want to add and click Next. The Add Monitor Step 2 dialog box is displayed.
Monitor
Name - enter or select the system to sample.
Host Name or IP - displays the host name or IP address of the selected system.
Add - displays the Add Monitored System dialog box for specifying a new system to monitor.
Edit - displays the Edit Monitored System dialog box for editing the selected system.
Monitored System Details - displays details about the monitored system. The information displayed is based on the type of data source being used.
Name - enter or select the data collector to use for sampling the system.
Host Name or IP - displays the host name or IP address of the selected system.
Port - displays the data collector port.
Add - displays the Add Data Collector dialog box for specifying a new data collector.
Edit - displays the Edit Data Collector dialog box for editing the selected data collector.
Collect data every - Specifies, in seconds, how often samples are taken for this monitor.
Enter the Target System and Data Collector or click the down arrow to select from a list.
Enter the collection interval and click Next. One of two possible Add Monitor Step 3 dialog boxes is displayed. If components require discovery, the following dialog box is displayed:
Monitored System
Discover - performs discovery on the monitored system. The Confirm Remove Components dialog box is displayed if there are any components that can no longer be found. Click OK to remove them or Cancel to keep them.
<component list> - lists all known components. These can be components that were discovered or manually entered when the system was configured in the system editor.
Click Discover to discover components, then select the components that you want to monitor and click Next.
The following dialog box is displayed as Add Monitor: Step 3 if components do not require discovery. It is displayed as Add Monitor: Step 4 if discovery was required.
Monitor - displays the monitor type and name.
Monitors - lists the monitors that are available. Deselect a monitor to disable it.
Discover Additional - finds more counters that are similar to the ones in the profile. This button is only available for Fujitsu Interstage SNMP and Hitachi Cosminexus profiles.
If you are using Fujitsu Interstage SNMP and have discovered additional counters, select the ones you want to use and click Add. Click OK when you are done.
The metrics in this profile are listed with a check box in front of each one. You can use all of these or a subset to monitor the selected system. Uncheck the box to disable the monitor.
Click Finish.
The Configurations dialog box is displayed. Click Test to make sure the monitor is configured correctly.
Click Close to exit the Configurations dialog box.
To create monitors using metrics:
Select Configurations from the ServerStats menu.
Select the configuration to which you want to add a Metric monitor and click New to display the Add Monitor Step 1 dialog box.
This dialog box is where you select the type of monitor you want to add. Expand the appropriate node and select the data source, metric, or metric profile that you want to add.
Expand the Metrics node, select the type of monitor you want to add and click Next. The Add Monitor Step 2 dialog box is displayed.
Monitor
Name - enter or select the system to sample.
Host Name or IP - displays the host name or IP address of the selected system.
Add - displays the Add Monitored System dialog box for specifying a new system to monitor.
Edit - displays the Edit Monitored System dialog box for editing the selected system.
Monitored System Details - displays details about the monitored system. The information displayed is based on the type of data source being used.
Name - enter or select the data collector to use for sampling the system.
Host Name or IP - displays the host name or IP address of the selected system.
Port - displays the data collector port.
Add - displays the Add Data Collector dialog box for specifying a new data collector.
Edit - displays the Edit Data Collector dialog box for editing the selected data collector.
Enter the Target System and Data Collector or click the down arrow to select from a list.
Enter the collection interval and click Next. One of two possible Add Monitor Step 3 dialog boxes is displayed. If components require discovery, the following dialog box is displayed:
Monitored System
Discover - performs discovery on the monitored system. The Confirm Remove Components dialog box is displayed if there are any components that can no longer be found. Click OK to remove them or Cancel to keep them.
<component list> - lists all known components. These can be components that were discovered or manually entered when the system was configured in the system editor.
Click Discover to discover components, then select the components that you want to monitor and click Next.
The following dialog box is displayed as Add Monitor Step 3 if components do not require discovery. It is displayed as Add Monitor Step 4 if discovery was required.
Monitor - displays the type and name of the monitor.
Monitors - lists the monitors that are available. Deselect a monitor to disable it.
The metric is listed with a check box. Uncheck the box to disable the monitor.
Click Finish.
The Configurations dialog box is displayed. Click Test to make sure the monitor is configured correctly.
Click Close to exit the Configurations dialog box.
Note:
To monitor disk performance on a Windows machine,Diskperf -yv must be enabled on that machine. See "Using Diskperf" for more information.To edit a monitor in a configuration:
Select Configurations from the ServerStats menu.
Select the configuration you want to edit.
Select the monitor that you want to edit and click Edit. The Edit Monitor dialog box is displayed.
Monitor
Properties - lists the properties specific to this monitor.
Discover - discovers monitors of the same type. Displays the Discovery dialog box for selecting a monitor.
Make any changes.
Click OK when you are done.
Click Close to exit the Configurations dialog box.
This section explains how to work with metric profiles.
You can add a user defined metric profile that contains any combination of default and user defined metrics.
Select Metric Profiles from the ServerStats menu to open the Metric Profiles dialog box.
New - displays the Add Profile dialog box for adding a user defined metric profile.
Edit - displays Edit Profile dialog box. This option is only available for user defined metric profiles. Default profiles cannot be edited.
Clone - displays the Clone Profile dialog box for copying a default profile to create a user defined metric profile that can be edited.
Delete - deletes the selected user defined metric profile. Default profiles cannot be deleted.
Metric Profile List - lists the default profiles and user defined metric profiles.
Name - displays the profile name.
Description - displays the profile description.
Category - displays the category to which the profile belongs.
Monitors - displays the monitors in the profile. Click a monitor to view its details.
Click New. The Add Metric Profile dialog box is displayed.
Name - the name of the profile.
Description - the profile's description.
Category - displays the category to which the profile belongs.
Metrics - displays the list of available metrics.
Add - adds the selected metric to the Selected Metrics list.
Selected Metrics - lists the selected metrics. Click the "x" in front of a metric to delete it from the list.
Ok - exits the dialog box and saves the profile.
Cancel - exits the dialog box without saving the profile.
Test - displays the Test Setup dialog box for setting test details.
Enter a name and description for the profile.
Add metrics by selecting them in the Metrics list and clicking Add.
To view a metric's details, select it in the Selected Metrics list.
Click the "x" in front a metric to delete it from the Selected Metrics list.
Click Test to test the metrics.
Click OK when you are done. Your new profile is listed in the User Defined category in the list of metric profiles.
You can edit user defined metric profiles. Default profiles cannot be changed. Changing a metric profile does not change it in any configurations using the metric profile.
Select Metric Profiles from the ServerStats menu.
Select the user defined metric profile that you want to edit and click Edit. The Edit Metric Profile dialog box is displayed.
Name - the name of the profile.
Description - the profile's description.
Category - displays the category to which the profile belongs.
Metrics - displays the list of available metrics.
Add - adds the selected metric to the Selected Metrics list.
Selected Metrics - lists the selected metrics. Click the "x" in front of a metric to delete it from the list.
Ok - exits the dialog box and saves the profile.
Cancel - exits the dialog box without saving the profile.
Test - displays the Test Setup dialog box for setting test details.
Add additional metrics by selecting them in the Metrics list and clicking Add.
Click the "x" in front of a metric to delete it from the list.
To view a metric's details, select it in the Selected Metrics list.
Click OK when you are done.
Cloning a profile lets you start with a default profile and create a user defined metric profile that you can customize for your needs by adding or deleting metrics.
Select Metric Profiles from the ServerStats menu.
Select the profile that you want to clone and click Clone. The Clone Metric Profile dialog box is displayed.
Name - the name of the profile.
Description - the profile's description.
Category - displays the category to which the profile belongs.
Metrics - displays the list of available metrics.
Add - adds the selected metric to the Selected Metrics list.
Selected Metrics - lists the selected metrics. Click the "x" in front of a metric to delete it from the list.
Ok - exits the dialog box and saves the profile.
Cancel - exits the dialog box without saving the profile.
Test - displays the Test Setup dialog box for setting test details.
Enter a name for the profile.
All of the metrics for the selected profile are automatically added to the Selected Metrics list. Click the "x" in front of a metric to delete it from the list.
Add additional metrics by selecting them in the Metrics list and clicking Add.
To view a metric's details, select it in the Selected Metrics list.
Click Test to test the metrics.
Click OK when you are done. Your new profile is listed in the User Defined category in the list of metric profiles.
Only user-defined metric profiles can be deleted. To delete a user-defined metric profile:
Select Metric Profiles from the ServerStats menu.
Select the user defined metric profile you want to delete and click Delete.
Click Yes when asked to confirm the deletion.
To view metric profiles:
Select Metric Profiles from the ServerStats menu.
Select the metric profile that you want to view. The monitors included in the profile are displayed in the right-hand pane.
Click a metric to display the View Metric dialog box.
Click Close when you are done.
To test metric profiles:
Select Metric Profiles from the ServerStats menu.
Select the profile you want to test and click Test. The Test Setup Dialog box is displayed.
Profile
Name - displays the name of the metric profile.
Name - enter or select the system to sample.
Host Name or IP - displays the host name or IP address of the selected system.
Add - displays the Add Monitored System dialog box for specifying a new system to monitor.
Edit - displays the Edit Monitored System dialog box for editing the selected system.
Monitored System Details - displays details about the monitored system. The information displayed is based on the type of data source being used.
Name - enter or select the data collector to use for sampling the system.
Host Name or IP - displays the host name or IP address of the selected system.
Port - displays the data collector port.
Add - displays the Add Data Collector dialog box for specifying a new data collector.
Edit - displays the Edit Data Collector dialog box for editing the selected data collector.
Collect data every - Specifies, in seconds, how often samples are taken for this monitor.
Enter the target system, data collector, and how often to collect data for the test. Some profiles may require additional information.
Click OK. The Test dialog box is displayed showing the results of the test.
This dialog displays the test results. It has the following information for each counter:
Counter Definition - displays the counter definition.
Last Value - displays the last collected value.
Time Stamp - displays the time that the last action happened. This could be the time of the last sample, or the time an error was encountered.
Click Close to exit the dialog box.
Click Close to exit Metric Profiles configuration.
This section explains how to work with metrics.
You can add metrics that can be used in any configuration. Metrics that you add are listed in the User Defined node of the Metrics tree. The Metrics dialog box has the following options:
New - displays the Add Metric dialog box for adding a user defined metric.
Edit - displays the Edit Metric dialog box. This option is only available for user defined metrics. Default metrics cannot be edited.
Clone - displays the Clone Metric dialog box for copying a default metric to create a user defined metric that can be edited.
Delete - deletes the selected user defined metric. Default metrics cannot be deleted.
Metrics List - lists user-defined metrics followed by the default metrics.
The right-hand pane displays the details about the selected metric and how it was configured.
The following sections explain how to add specific metric types:
Select Metrics from the ServerStats menu.
Click New. The Add Metrics dialog box is displayed.
Metric type - lists the available data sources.
Add - displays the Add Metric dialog box for adding metrics.
Metrics - lists the selected metrics. When you click Close, each metric will be listed in the User Defined node of the ServerStats dialog box.
Select Com+ and click Add. The Add Metric dialog box is displayed.
Name - enter a name for the metric.
Description - enter a description of the metric.
Category - displays the type of metric.
Note:
With the exception of the Sample Multiplier field, all fields are filled in as a result of discovering counters.Sample Multiplier - enter the multiplier you want to be applied to the data that is collected. Setting the sample multiplier to 1 means that the data will be reported as is. If the metric measurement is expressed in kilobytes, setting the sample multiplier to 1024 translates it to bytes. If the metric measurement is expressed in milliseconds, setting the sample multiplier to .001 translates it to seconds.
Translation Type- Translation Type controls how a metric's data is displayed in Reports.
Note:
Rate (minutes) translates data sources that return their values as an endlessly increasing counter. If the data source does not return data this way, use No Translation.Discover Counters - displays the Setup Discovery dialog box for selecting the target system and data collector to use for discovery. A list of discovered metrics is displayed in the Discovery dialog box for selecting the metric to use.
Enter a name and description for the metric.
If you want to find metrics on a system, set Is object discovery needed to Yes, select the discovery type, and click Discover Counters, otherwise, go to step 8. The Setup Discovery dialog box is displayed.
Metric - displays the name of the data source.
Name - enter or select the system to sample.
Host Name or IP - displays the host name or IP of the selected system.
Add - displays the Add Monitored System dialog box for specifying a new system to monitor.
Edit - displays the Edit Monitored System dialog box for editing the selected system.
Name - enter or select the data collector to use for sampling the system.
Host Name or IP - displays the host name or IP address of the selected system.
Port - displays the data collector port.
Add - displays the Add Data Collector dialog box for specifying a new data collector.
Edit - displays the Edit Data Collector dialog box for editing the selected data collector.
Enter the server location information and click OK. The Com+ Discovery dialog box is displayed.
Select the counters you want to use and click OK.
If you do not need to discover metrics, enter the Metric properties and click Finish.
You can then test the metric by clicking Test and specifying the test parameters.
Select Metrics from the ServerStats menu.
Click New. The Add Metrics dialog box is displayed.
Metric type - lists the available data sources.
Add - displays the Add Metric dialog box for adding metrics.
Metrics - lists the selected metrics. When you click Close, each metric will be listed in the User Defined node of the ServerStats dialog box.
Select Database and click Add. The Add Metric dialog box is displayed.
Name - enter a name for the metric.
Description - enter a description of the metric.
Category - displays the type of metric.
Metric Properties
Query - Enter a valid database statement. For example, you can enter the following Oracle SELECT statement:
select value from v$sysstat where statistic# = 1
If your database server supports returning a result set from a stored procedure you can call the procedure. For example, the following SQL Server stored procedure, present in the database, returns a result set (not an output parameter) showing the configured sample rate (samples/minute):
p_computeSampleRate
Result Pattern - enter the Perl expression for the value that should be returned for the specified query.
Sample Multiplier - enter the multiplier you want to be applied to the data that is collected. Setting the sample multiplier to 1 means that the data will be reported as is. If the metric measurement is expressed in kilobytes, setting the sample multiplier to 1024 translates it to bytes. If the metric measurement is expressed in milliseconds, setting the sample multiplier to .001 translates it to seconds.
Translation Type - Translation Type controls how a metric's data is displayed in Reports.
Note:
Rate (minutes) translates data sources that return their values as an endlessly increasing counter. If the data source does not return data this way, use No Translation.Enter a name and description for the metric.
Enter the Metric properties.
You can test the metric by clicking Test and specifying the test parameters.
Click Finish.
Enterprise Manager metrics specify the URL query string parameters to use for an Enterprise Manager instance when accessing Enterprise Manager Diagnostic metrics from the Oracle Load Testing reports. See Appendix A, "Oracle Enterprise Manager Metric Profile" for additional information.
Before configuring Enterprise Manager metrics in Oracle Load Testing ServerStats, be sure the following prerequisites have been completed.
You have and Enterprise Manager Grid Control 11.1 instance set up and available to be accessed.
You have AD4J manager configured for the Enterprise Manager Grid Control 11.1 instance.
You have AD4J agent on the targets where the application under test will be running.
For WebLogic Domain Metrics or WebLogic JVM Metrics, you have the name of the "target" or "targets" of Enterprise Manager/AD4J deployment (the Web application being load tested and managed/monitored by Enterprise Manager).
Note:
See the Enterprise Manager and AD4J documentation for details about setting up and configuring Enterprise Manager and AD4J or contact the Enterprise Manager instance administrator.For Oracle Database Metrics, you must have the name of the instance of the database you wish to view.
Additional Oracle Load Testing Steps
In addition to the Prerequisites required of the Enterprise Manager/AD4J instance, the following additional general steps are required to use the Enterprise Manager data source in Oracle Load Testing:
Define a "Monitored System" in Oracle Load Testing and specify the base URL of the Enterprise Manager instance from which to retrieve Weblogic Domain Metrics, Weblogic JVM Metrics, or Oracle Database Metrics. See the Oracle Load Testing User's Guide for information about defining monitored systems.
Add a new ServerStats metric or metrics specifying the target or targets setup in the Enterprise Manager instance (the string from the Name column of the Middleware section of the Targets tab of the Enterprise Manager instance for Weblogic Domain or JVM metrics or the name of the database instance to view on the Enterprise Manager Database Historical Performance page for Oracle Database metrics).
Create a new ServerStats configuration or configurations and include the Enterprise Manager metric or metrics and select the Enterprise Manager data source "Monitored System".
Once you have defined a "Monitored System, created the ServerStats metric, and created a ServerStats configuration, build a Scenario in Oracle Load Testing with the script or scripts to playback against the Web application-under-test being monitored by the Enterprise Manager instance.
On the Set up Autopilot tab, select the ServerStats configuration you defined for the Enterprise Manager "Monitored System" in the ServerStats Configuration section.
Start the a load test against the application-under-test.
At the conclusion of the load test (or during the load test), click the Create Reports tab and select the session you started in the Autopilot tab.
Expand the Available Data Series and the Enterprise Manager Diagnostics reports-counters tree.
Note:
Sessions with Oracle DB Metrics and Enterprise Manager URL that were run using an Oracle Load Testing version prior to version 9.30 will not automatically show the links for ADDM & AWR reports. To show the ADDM & AWR links under Enterprise Manager Diagnostics, generate the ADDM & AWR reports using the Reports sub-tab of the Create Reports tab.Double-click the metrics below the Enterprise Manager Diagnostics in the reports-counters tree to launch an external browser window and open the Enterprise Manager login screen.
After you log into the Enterprise Manager instance, the page is redirected to the diagnostics page inside of Enterprise Manager specified by the combination of the base URL and the parameters specified in the Oracle Load Testing ServerStats metric. The page shows the data for the filtered time (start time and end time = Epoch time), as follows:
If the session is ended, from start time to end time.
If the session is still running, from start time to the current time.
Additional Oracle Database Metrics Notes
At the beginning and end of each load session to which one or more Oracle database metrics are attached, Oracle Load Testing takes a database "snapshot". The second snapshot is used to create a "baseline" which saves the database diagnostic information between the two snapshots. The snapshot and baseline IDs are stored with the Oracle Load Testing session information. This allows links to Enterprise Manager to display useful data past the regular data retention of the target database.
For load sessions to which one or more Oracle database metrics are attached, the View Run Graphs and Create Reports tab includes Database Diagnostics graphs.
An "Enterprise Manager Diagnostics" node is also added to the session tree with the database monitor. Double-clicking this monitor opens a new browser for Enterprise Manager, displaying (after login) the database drilldown for the database selected.
To add Enterprise Manager metrics:
Select Metrics from the ServerStats menu.
Click New. The Add Metrics dialog box is displayed.
Metric type - lists the available data sources.
Add - displays the Add Metric dialog box for adding metrics.
Metrics - lists the selected metrics. When you click Close, each metric will be listed in the User Defined node of the ServerStats dialog box.
Select Enterprise Manager and click Add. The Add Metric dialog box is displayed.
Name - enter a name for the metric.
Description - enter a description of the metric.
Category - displays the type of metric.
Metric Properties
Metric type - (required) select a metric type.
Weblogic Domain Metrics - this type queries for Enterprise Manager Weblogic Domain Metrics by adding the weblogic_domain query string parameter to the base Enterprise Manager URL specified in the Enterprise Manager data source in Oracle Load Testing Monitored Systems.
Weblogic JVM Metrics - this type queries for Enterprise Manager Weblogic JVM Metrics by adding the weblogic_j2eeserver query string parameter to the base Enterprise Manager URL specified in the Enterprise Manager data source in Oracle Load Testing Monitored Systems.
Oracle Database Metrics - this type uses the Target to point to a specific database instance as a parameter to the base Enterprise Manager URL specified in the Enterprise Manager data source in Oracle Load Testing Monitored Systems. The URL links to the Enterprise Manager Database Historical Performance page.
Target - (required) specifies the WebLogic domain or JVM or Oracle Database from which to gather metrics. For Domain or JVM metrics, log into the Enterprise Manager instance and select the Targets tab, then select Middleware. Copy the Name string from the Enterprise Manager Middleware page to this field to specify the target. For Oracle Database Metrics, enter the instance of the database you wish to view.
Method Name - (optional) specifies the Java method name string of a specific Java method into which to drill down. The available Method Names are dependent upon the target specified in the Enterprise Manager instance. Method names will need to provided by the Enterprise Manager instance administrator. If specified, the methodName parameter is added to the base Enterprise Manager URL specified in the Enterprise Manager data source in Oracle Load Testing Monitored Systems. If omitted, the main page for the specified type of metric is shown.
Request Name - (optional) specifies the named HTTP request string of a specific request to which to drill down. The available Request Names are dependent upon the target specified in the Enterprise Manager instance. Request names will need to provided by the Enterprise Manager instance administrator. If specified, the requestName parameter is added to the base Enterprise Manager URL specified in the Enterprise Manager data source in Oracle Load Testing Monitored Systems. If omitted, the main page for the specified type of metric is shown.
Enter a name and description for the metric.
Enter the Metric properties.
You can test the metric by clicking Test and specifying the test parameters.
Click Finish.
To add an IBM WebSphere metric:
Select Metrics from the ServerStats menu.
Click New. The Add Metrics dialog box is displayed.
Metric type - lists the available data sources.
Add - displays the Add Metric dialog box for adding metrics.
Metrics - lists the selected metrics. When you click Close, each metric will be listed in the User Defined node of the ServerStats dialog box.
Select IBM WebSphere PMI and click Add. The Add Metric dialog box is displayed.
Name - enter a name for the metric.
Description - enter a description of the metric.
Category - displays the type of metric.
Metric Properties
Document - specify the URL to use as the root for the queries to identify counters. For example, wasPerfTool/servlet/perfservlet.
Server- specify the server instance that you want to talk to.
Sample Multiplier - enter the multiplier you want to be applied to the data that is collected. Setting the sample multiplier to 1 means that the data will be reported as is. If the metric measurement is expressed in kilobytes, setting the sample multiplier to 1024 translates it to bytes. If the metric measurement is expressed in milliseconds, setting the sample multiplier to .001 translates it to seconds.
Translation Type - Translation Type controls how a metric's data is displayed in Reports.
No Translation - data is displayed as it is provided by the metric's data source.
Rate (minutes) - data is presented as a number, per minute. For example, if the time interval between two samples was 10 minutes, and 50 errors were found, the Rate (minutes) would be five (5) errors per minute.
Note:
Rate (minutes) translates data sources that return their values as an endlessly increasing counter. If the data source does not return data this way, use No Translation.Enter a name and description for the metric.
Enter the Metric properties and click Discover Counters. The Setup Discovery dialog box is displayed.
Metric - displays the type of the data source.
Name - enter or select the system to sample.
Host Name or IP - displays the host name or IP address of the selected system.
Add - displays the Add Monitored System dialog box for specifying a new system to monitor.
Edit - displays the Edit Monitored System dialog box for editing the selected system.
IBM WebSphere PMI - displays details about the monitored system. The information displayed is based on the type of data source being used.
Name - enter or select the data collector to use for sampling the system.
Host Name or IP - displays the host name or IP address of the selected system.
Port - displays the data collector port.
Add - displays the Add Data Collector dialog box for specifying a new data collector.
Edit - displays the Edit Data Collector dialog box for editing the selected data collector.
Enter the server location information and properties for discovery and click OK. The WebSphere Discovery dialog box is displayed.
Select the counters you want to use and click OK.
You can test the metric by clicking Test and specifying the test parameters.
Click Finish.
Select Metrics from the ServerStats menu.
Click New. The Add Metrics dialog box is displayed.
Metric type - lists the available data sources.
Add - displays the Add Metric dialog box for adding metrics.
Metrics - lists the selected metrics. When you click Close, each metric will be listed in the User Defined node of the ServerStats dialog box.
Select JMX and click Add. The Add Metric dialog box is displayed.
Name - enter a name for the metric.
Description - enter a description of the metric.
Category - displays the type of metric.
Filter MBeans By - select the server type by which you want to filter MBeans or select All Counters to return all supported MBeans.
Discovery MBeans - select the type of MBeans to discover or select All Counters to discover all types of MBeans.
Sample Multiplier - enter the multiplier you want to be applied to the data that is collected. Setting the sample multiplier to 1 means that the data will be reported as is. If the metric measurement is expressed in kilobytes, setting the sample multiplier to 1024 translates it to bytes. If the metric measurement is expressed in milliseconds, setting the sample multiplier to .001 translates it to seconds.
Translation Type - Translation Type controls how a metric's data is displayed in Reports.
Note:
Rate (minutes) translates data sources that return their values as an endlessly increasing counter. If the data source does not return data this way, use No Translation.Enter a name and description for the metric.
Enter the metric properties and click Discover Counters, otherwise go to step 8. The Setup Discovery dialog box is displayed.
Metric - displays the name of the data source.
Name - enter or select the system to sample.
Host Name or IP - displays the host name or IP address of the selected system.
Add - displays the Add Monitored System dialog box for specifying a new system to monitor.
Edit - displays the Edit Monitored System dialog box for editing the selected system.
JMX - displays details about the monitored system. The information displayed is based on the type of data source being used.
Name - enter or select the data collector to use for sampling the system.
Host Name or IP - displays the host name or IP address of the selected system.
Port - displays the data collector port.
Add - displays the Add Data Collector dialog box for specifying a new data collector.
Edit - displays the Edit Data Collector dialog box for editing the selected data collector.
Enter the server location information and properties for discovery and click OK. The JMX Discovery dialog box is displayed.
Select the counters you want to use and click OK.
If you do not need to discover metrics, enter the Metric properties and click Finish.
You can then test the metric by clicking Test and specifying the test parameters.
Select Metrics from the ServerStats menu.
Click New. The Add Metrics dialog box is displayed.
Metric type - lists the available data sources.
Add - displays the Add Metric dialog box for adding metrics.
Metrics - lists the selected metrics. When you click Close, each metric will be listed in the User Defined node of the ServerStats dialog box.
Select Windows Performance Monitor (Perfmon) and click Add. The Add Metric dialog box is displayed.
Name - enter a name for the metric.
Description - enter a description of the metric.
Category - displays the type of metric.
Is system discovery needed? - select Yes when you want to discover metrics.
System component to discover - select the type of discovery.
Discover Counters - displays the Setup Discovery dialog box for selecting the target system and data collector to use for discovery. A list of discovered metrics is displayed in the Discovery dialog box for selecting the metric to use.
Counter Name - specify the counter name. For example, % Processor Time. You must enter the counter name exactly as it is displayed in the Perfmon editor. Be careful to check for spaces and case in the Counter name.
Instance Name - if the metric has an instance associated with it, specify it here.
Object Name - specify the object name. For example, Processor or Memory. You must enter the object name exactly as it is displayed in the Perfmon editor. Be careful to check for spaces and case in the Object name.
Sample Multiplier - enter the multiplier you want to be applied to the data that is collected. Setting the sample multiplier to 1 means that the data will be reported as is. If the metric measurement is expressed in kilobytes, setting the sample multiplier to 1024 translates it to bytes. If the metric measurement is expressed in milliseconds, setting the sample multiplier to .001 translates it to seconds.
Translation Type - Translation Type controls how a metric's data is displayed in Reports.
Note:
Rate (minutes) translates data sources that return their values as an endlessly increasing counter. If the data source does not return data this way, use No Translation.Enter a name and description for the metric.
If you want to find metrics on a system, set Is system discovery needed to Yes, select the discovery type, and click Discover Counters, otherwise, go to step 8. The Setup Discovery dialog box is displayed.
Metric - displays the name of the data source.
Name - enter or select the system to sample.
Host Name or IP - displays the host name or IP address of the selected system.
Add - displays the Add Monitored System dialog box for specifying a new system to monitor.
Edit - displays the Edit Monitored System dialog box for editing the selected system.
Monitored System Details - displays details about the monitored system. The information displayed is based on the type of data source being used.
Name - enter or select the data collector to use for sampling the system.
Host Name or IP - displays the host name or IP address of the selected system.
Port - displays the data collector port.
Add - displays the Add Data Collector dialog box for specifying a new data collector.
Edit - displays the Edit Data Collector dialog box for editing the selected data collector.
Enter the server location information and properties for discovery and click OK. The Perfmon Discovery dialog box is displayed.
Performance object - select the performance object you want to monitor.
<counter list> - lists the counters associated with the selected performance object. Select the counter.
<instance list> - lists the instances associated with the selected counter object. Select the instance.
Counters - displays the selected counters.
Select the counters you want to use and click OK.
If you do not need to discover metrics, enter the Metric properties and click Finish.
You can then test the metric by clicking Test and specifying the test parameters.
Note:
To monitor disk performance on a Windows machine,Diskperf -yv must be enabled on that machine. See "Using Diskperf" for more information.Select Metrics from the ServerStats menu.
Click New. The Add Metrics dialog box is displayed.
Metric type - lists the available data sources.
Add - displays the Add Metric dialog box for adding metrics.
Metrics - lists the selected metrics. When you click Close, each metric will be listed in the User Defined node of the ServerStats dialog box.
Select Ping and click Next. The Add Metric Step 2 of 2 dialog box is displayed.
Name - enter a name for the metric.
Description - enter a description of the metric.
Category - displays the type of metric.
Metric Properties
Measurement - Specifies the metric to use for the Ping monitor. Select the metric to use: Average Round Trip Time (PingAvgRTT) or Percentage of Success (PingPercentSuccess).
Length - specify how many bytes should be included in each echo request packet.
Time to Live - Specifies the maximum number of router hops permitted. If the echo request takes more than the maximum number of hops, it is thrown away and the Ping attempt is treated as a failure.
Sample Multiplier - enter the multiplier you want to be applied to the data that is collected. Setting the sample multiplier to 1 means that the data will be reported as is. If the metric measurement is expressed in kilobytes, setting the sample multiplier to 1024 translates it to bytes. If the metric measurement is expressed in milliseconds, setting the sample multiplier to .001 translates it to seconds.
Translation Type - Translation Type controls how a metric's data is displayed in Reports.
Note:
Rate (minutes) translates data sources that return their values as an endlessly increasing counter. If the data source does not return data this way, use No Translation.Enter a name and description for the metric.
Enter the Metric properties.
You can test the metric by clicking Test and specifying the test parameters.
Click Finish.
Select Metrics from the ServerStats menu.
Click New. The Add Metrics dialog box is displayed.
Metric type - lists the available data sources.
Add - displays the Add Metric dialog box for adding metrics.
Metrics - lists the selected metrics. When you click Close, each metric will be listed in the User Defined node of the ServerStats dialog box.
Select SNMP and click Add. The Add Metric dialog box is displayed.
Name - enter a name for the metric.
Description - enter a description of the metric.
Category - displays the type of metric.
Is system discovery needed? - select Yes when you want to discover metrics.
System component to discover - select the type of discovery.
Name - enter the metric name.
Second OID for ratio - enter the second object ID to retrieve if you are using a ratio. This OID is the divisor. For example, if you want to calculate the percentage of disk space available, you must divide the amount of space used by the total amount available.
Search for string - Enter the string to search for in the OID column that you specify below. This setting applies only if TableGet is selected.
In OID column - Enter the column to search in for the string you specified above. This setting applies only if TableGet is selected.
Datatype of second OID - select the datatype of the second OID.
Sample Multiplier - enter the multiplier you want to be applied to the data that is collected. Setting the sample multiplier to 1 means that the data will be reported as is. If the metric measurement is expressed in kilobytes, setting the sample multiplier to 1024 translates it to bytes. If the metric measurement is expressed in milliseconds, setting the sample multiplier to .001 translates it to seconds.
Translation Type - Translation Type controls how a metric's data is displayed in Reports.
Note:
Rate (minutes) translates data sources that return their values as an endlessly increasing counter. If the data source does not return data this way, use No Translation.Discover Counters - displays the Setup Discovery dialog box for selecting the target system and data collector to use for discovery. A list of discovered metrics is displayed in the Discovery dialog box for selecting the metric to use.
Enter a name and description for the metric.
If you want to find metrics on a system, set Is system discovery needed to Yes, select the discovery type, and click Discover Counters, otherwise, go to step 8. The Setup Discovery dialog box is displayed.
Metric - displays the name of the data source.
Name - enter or select the system to sample.
Host Name or IP - displays the host name or IP address of the selected system.
Add - displays the Add Monitored System dialog box for specifying a new system to monitor.
Edit - displays the Edit Monitored System dialog box for editing the selected system.
Monitored System Details - displays details about the monitored system. The information displayed is based on the type of data source being used.
Name - enter or select the data collector to use for sampling the system.
Host Name or IP - displays the host name or IP address of the selected system.
Port - displays the data collector port.
Add - displays the Add Data Collector dialog box for specifying a new data collector.
Edit - displays the Edit Data Collector dialog box for editing the selected data collector.
Enter the server location information and properties for discovery and click OK. The SNMP Discovery dialog box is displayed.
Validate against target machine - applies the SNMP metrics in the selected MIB file to the selected system.
MIB File - select the MIB file to use.
Upload File - displays the Upload File dialog box for uploading a mib file to the server.
Counters - displays information about the selected counters.
Select the counters you want to use and click OK.
If you do not need to discover metrics, enter the Metric properties and click Finish.
You can then test the metric by clicking Test and specifying the test parameters.
Select Metrics from the ServerStats menu.
Click New. The Add Metrics dialog box is displayed.
Metric type - lists the available data sources.
Add - displays the Add Metric dialog box for adding metrics.
Metrics - lists the selected metrics. When you click Close, each metric will be listed in the User Defined node of the ServerStats dialog box.
Select URL and click Add. The Add Metric dialog box is displayed.
Name - enter a name for the metric.
Description - enter a description of the metric.
Category - displays the type of metric.
URL - If URL Usage is set to Specify, type the URL for the web page you want to check. The URL must be specified with the full protocol designation of http or https. For example: http://www.company.com.
If you use Get as the HTTP Method (the default), simply include any additional parameters you want to include as part of the URL string, for example:
POST - the Post method, usually associated with a form, allows a much larger amount of information to be associated with the request.
GET - include any additional query strings as part of the URL address.
Note:
Some servers limit the length of URL and query strings to about 240 characters.Post Data - If you select Post as the URL Method, you can add a series of name-value pairs. For example, a URL generated after completing a form may appear as follows:
POST http://www.company.com/cgi-bin/guestbook.pl ...(additional headers) name=Harold&nickname=Harry
To reference this page, enter name=Harold&nickname=Harry in this field.
User Agent - you can specify a particular user agent when you monitor a URL. When you configure a User Agent, the browser and operating system you specify is added to the header of the URL request. This allows you to test pages designed for a specific browser URL and confirm that a page designed for multiple browsers works appropriately for each of them.
False - select this option if you want the URL test to prevent the use of cookies when accessing the page.
True - select this option if you want to allow the URL monitor to support cookies as part of the URL request. A fresh cookie is retrieved each time the test is run.
Custom Cookie - type in a cookie value for the page you are monitoring. If you supply a particular value, remember that the cookie is saved and can become out of date. Refresh cookie requests are ignored.
Types other than HTML and images are also classified as objects.
Include image download times - calculates the URL availability and access time with retrieval of embedded images (such as .gif and .jpeg files and references within <img> tags).
Include object download times - calculates URL availability and access time with retrieval of embedded objects (such as ActiveX objects and Java applets). Oracle Load Testing measures the time taken to retrieve data used by objects, but does not include the time needed to retrieve any executable file required in order to interpret the data.
Result of Perl Expression - enter the Perl expression to use if you have selected Result of Perl Expression as the metric type.
Username - if the URL specified requires a name and password for access, enter the name in this field.
Password - if the URL specified requires a name and password for access, enter the password in this field.
Enable Proxy- select this checkbox if your network makes use of a proxy server.
Proxy Host - specify the name or IP address of the proxy server.
Proxy Password - the proxy server login password.
Sample Multiplier - enter the multiplier you want to be applied to the data that is collected. Setting the sample multiplier to 1 means that the data will be reported as is. If the metric measurement is expressed in kilobytes, setting the sample multiplier to 1024 translates it to bytes. If the metric measurement is expressed in milliseconds, setting the sample multiplier to .001 translates it to seconds.
Translation Type - Translation Type controls how a metric's data is displayed in Reports.
Note:
Rate (minutes) translates data sources that return their values as an endlessly increasing counter. If the data source does not return data this way, use No Translation.Enter a name and description for the metric.
Enter the Metric properties.
You can test the metric by clicking Test and specifying the test parameters.
Click Finish.
To add a Virtual Agent metric:
Select Metrics from the ServerStats menu.
Click New. The Add Metrics dialog box is displayed.
Metric type - lists the available data sources.
Add - displays the Add Metric dialog box for adding metrics.
Metrics - lists the selected metrics. When you click Close, each metric will be listed in the User Defined node of the ServerStats dialog box.
Select Virtual Agent and click Add. The Add Metric dialog box is displayed.
Name - enter a name for the metric.
Description - enter a description of the metric.
Category - displays the type of metric.
Is system discovery needed? - select Yes when you want to discover metrics.
System component to discover - select the type of discovery.
Description - enter a description.
Command Line - specifies the command to execute on the host machine.
Matching Regexp - specifies a Perl expression to use to report the data returned from the executable program.
Sample Multiplier - enter the multiplier you want to be applied to the data that is collected. Setting the sample multiplier to 1 means that the data will be reported as is. If the metric measurement is expressed in kilobytes, setting the sample multiplier to 1024 translates it to bytes. If the metric measurement is expressed in milliseconds, setting the sample multiplier to .001 translates it to seconds.
Translation Type - Translation Type controls how a metric's data is displayed in Reports.
Note:
Rate (minutes) translates data sources that return their values as an endlessly increasing counter. If the data source does not return data this way, use No Translation.Enter a name and description for the metric.
Enter the Metric properties.
You can test the metric by clicking Test and specifying the test parameters.
Click Finish.
You can add other SNMP metrics if you have the Object ID for the metric or if you have uploaded a device vendor MIB file to Oracle Load Testing.
To add other SNMP metrics:
Select Metrics from the ServerStats menu.
Select New. The Add Metric dialog box is displayed.
Select SNMP and click Add.
Enter the name and Object ID of the metric. If you uploaded a MIB file, skip to Discover Counters.
Enter any additional information if necessary.
Click Discover Counters.
Click OK.
Click OK.
Select the MIB file.
Select a counter and click Add for each counter you wish to add.
Click OK and Close as necessary to exit. The Metric is added to the User Defined metrics tree. See Section 1.8.1.8, "Adding SNMP Metrics" for additional information.
You can upload MIB files obtained from a device vendor to Oracle Load Testing Application Server.
To upload MIB files:
Select Upload File from the Tools menu.
Select SNMP MIB File as the file type.
Click Browse then select the file and click Open.
Click Upload.
Define the metrics you wish to use. See Section 1.8.1.11, "Adding Other SNMP Metrics" for additional information.
Only user-defined metrics can be edited. Default metrics cannot be changed. Changing a metric changes it in any configuration that uses it.
To edit user-defined metrics:
Select Metrics from the ServerStats menu.
Select the user defined metric you want to edit and click Edit. The Edit Metric dialog is displayed showing the properties pertinent to the selected metric.
Make any necessary changes.
You can test the metric by clicking Test and specifying the test parameters.
Click OK.
When you clone a default metric you create a user defined metric that can be edited, saved, and used in configurations.
To clone a metric:
Select Metrics from the ServerStats menu.
Select the metric you want to clone and click Clone. The Clone Metric dialog box is displayed. This dialog box displays name and description details about the metric as well as metric discovery and property information when applicable.
Make any changes and click OK. The metric is listed in the user defined node of the metric tree.
User defined metrics can be deleted. Default metrics cannot be deleted.
To delete a metric:
Select Metrics from the ServerStats menu.
Select the user defined metric that you want to delete and click Delete.
Click Yes when asked to confirm the deletion.
To test a metric:
Select Metrics from the ServerStats menu.
Select the metric you want to test and click Test. The Test Setup dialog box is displayed for configuring how you want to test the metric.
Name - displays the name of the metric profile.
Name - enter or select the system to sample.
Host Name or IP - displays the host name or IP address of the selected system.
Add - displays the Add Monitored System dialog box for specifying a new system to monitor.
Edit - displays the Edit Monitored System dialog box for editing the selected system.
Monitored System Details - displays details about the monitored system. The information displayed is based on the type of data source being used.
Name - enter or select the data collector to use for sampling the system.
Host Name or IP - displays the host name or IP address of the selected system.
Port - displays the data collector port.
Add - displays the Add Data Collector dialog box for specifying a new data collector.
Edit - displays the Edit Data Collector dialog box for editing the selected data collector.
Collect data every - Specifies, in seconds, how often samples are taken for this monitor.
Enter the server location and collection interval information and click OK. The Test dialog box is displayed.
This dialog displays the test results. It has the following information for each counter:
Counter Definition - displays the counter definition.
Last Value - displays the last collected value.
Time Stamp - displays the time that the last action happened. This could be the time of the last sample, or the time an error was encountered.
Click Close to exit the Test dialog box.
Click Close to exit Metrics configuration.
You can view metric descriptions and configuration details from both the Metric Profiles dialog box and the Metrics dialog box.
To view metrics from the Metric Profiles dialog box:
Select Metrics Profiles from the ServerStats menu.
Open the metric profile containing the metric that you want to view.
Select the metric from the right-hand pane.
Name - displays the metric name.
Description - displays the metric's description.
Category - displays the metric's category.
Data Source - displays the metric's data source.
Metric properties - displays the properties particular to this metric and how they are configured. Refer to the appropriate section under "Adding Metrics" for property descriptions.
Metric Discovery - displays whether the object needs to be discovered and the object type to discover.
Click Close to exist the View Metric dialog box.
To view metrics from the Metrics dialog box:
Select Metrics from the ServerStats menu.
Select the metric you want to view. The details about the metric and how it was configured are displayed in the right-hand pane.
Click Close to exit the Metrics configuration.
You can view the status of ServerStats during a running session. To view ServerStats status:
Select ServerStats Display from the ServerStats menu to display the ServerStats Display dialog box.
This dialog box displays the status of ServerStats for a running test.
Counter Definition - displays the counter description.
Last Value - displays the last sampled value.
Time Stamp - displays when the last value was sampled.
Error - displays an error message if one has been encountered.
Click Close when you are done.
Diskperf is a command that enables the Windows Perfmon counter that measures computer disk performance.
You will probably have to enable Diskperf on Windows 2000 machines when you have monitors that use Perfmon. These counters are typically enabled by default on a Windows NT machine, but disabled by default on a Windows 2000 machine.
To execute the Diskperf command:
Log on with administrative rights to the NT or Windows 2000 machine whose disk performance you want to monitor.
At the command line, type one of the following:
Non-RAID or hardware RAID PCs: diskperf -y
Software RAID PCs: diskperf -y e
Windows 2000 PCs: diskperf -yv
Note:
The complete list of options for either system can be found by runningdiskperf -?Press Enter.
Restart the computer.