Share this page

# Metrics and tags

This section describes how to view and collect metrics for popular monitoring tools: Datadog, Splunk, New Relic, and CloudWatch. Since the integrations are bi-directional, you can see metrics in your tool's interface, and in Controller and Analysis graphs.

In this topic:

## Metrics

The run information is divided into metrics. Metrics for OpenText Professional Performance Engineering data begin with loadrunner. The available metrics are listed in the tool's Metrics section.

Available metrics include the following:

Metric | Details
--- | ---
loadrunner.vusers.running | Number of Vusers currently running.
loadrunner.vusers.ready | Number of Vusers ready to run.
loadrunner.vusers.finished | Number of Vusers that have finished running.
loadrunner.vusers.error | Number of Vusers that have failed with errors.
loadrunner.total.transactions.passed.per.sec | Total transactions passed per second.
loadrunner.transaction.response_time | Specific transaction response time.
loadrunner.transaction.passed | Number of successful executions of the transaction.
loadrunner.transaction.failed | Number of failed executions of the transaction.
loadrunner.transaction.stopped | Number of stopped executions of the transaction.

## Tags

Tags enable you to aggregate and filter data. Different tags are automatically applied to OpenText Professional Performance Engineering run metrics and to scenario information.

Tags are available for the Datadog, Splunk, and New Relic tools but not CloudWatch.

### Scenario information tags

The following tags are applied to scenario information.

Note: To ensure that the scenario information tags are applied, you must install the LoadRunner Run Info Pipeline add on in your tool.

Tag key | Value
--- | ---
lr_hostname | Name of the Controller machine running the scenario.
lr_scenario_load_behavior | Initialization behavior of the Vusers.
lr_scenario_mode | Schedule type: scenario scheduling or group scheduling.
lr_scenario_type | Manual or goal-oriented scenario.
lr_service | The component running the scenario.
lr_version | Version of Controller running the scenario.

### Run metric tags

The following tags are applied to run metrics.

Tag key | Value
--- | ---
host | Name of the Controller machine running the scenario.
transaction_name | Transaction name from the Vuser script.

Note: Limitations apply to metric tags, such as maximum length and supported characters. If a tag value does not meet the requirements, the value is changed within your tool. For example, if a transaction name includes an unsupported special character, the character is converted to an underscore: _

For more details, see your external tool's documentation.

## See also

- Datadog monitor
- Integration with Splunk
- Integration with Datadog
- Integration with New Relic

https://admhelp.microfocus.com Professional Performance Engineering,VuGen 8942
Tips to improve your search results... OpenText™ Professional Performance Engineering Help Center OpenText™ Professional Performance Engineering Help 26.1-26.3 All View Local Help Center View Online Help Center Version: