Share this page

# Observability metrics

You can configure Controller to push observability metrics and data from scenario runs to an OpenTelemetry Collector. The observability data can be sent for scripts of all protocols.

Tip: Observability metrics can also be sent during script replay in VuGen. For details, see Observability metrics in the VuGen Help Center.

In this topic:

## Push data to an OpenTelemetry Collector

Configure Controller to push data to an OpenTelemetry Collector.

To configure Controller to push data to an OpenTelemetry Collector:

1. In the Controller toolbar, select Tools > External metrics > Observability configuration.

2. In the Observability Options dialog box, select Enable Observability during the load test.

3. Enter the following information.

   Field | Details
   --- | ---
   % of all relevant Vusers in the current scenario | Percentage of Vusers in the scenario whose data is sent to the observability collector. Note: Data is sent from at least 1 Vuser. If the specified percentage is equal to less than 1 Vuser in the current scenario, then data is sent from 1 Vuser. Setting a high percentage may impact load generator performance.
   Observability collector | Name and port number of the collector, beginning with grpc:// or http://, for example: `http://my-collector:4318`. When using the OTLP over HTTP protocol, the full path must be provided for the endpoint, including the appropriate OTLP signal path. For example: `http://collector-host:4318/v1/traces`
   TLS CA certificate | File path of the TLS CA certificate to connect to the collector (if required). Tip: You can use a relative file path to indicate the certificate. If the certificate is saved in the same folder as the script, you only need to indicate the file name of the certificate.
   Authorization header | Authorization header to send data to the collector (if required).

   When the scenario is run, telemetry data is sent per transaction to the collector. Transactions are tagged with the transaction name, Vuser number, and other information. Both gRPC and HTTP exporters are supported.

   For Web - HTTP/HTML scripts, a traceparent HTTP header is also automatically added. For details, see below.

## Traceparent header in Web - HTTP/HTML scripts

When you run a Web - HTTP/HTML script with observability metrics enabled, each HTTP request is reported to the collector as a transaction. A traceparent header is automatically added to each request, which enables you to track the flow of the request and correlate related observability data.

If a Web - HTTP/HTML script has existing traceparent headers included in its HTTP requests, these headers might conflict with the traceparent headers created to be sent with the observability data. We recommend deleting any existing traceparent headers from the script before running the script.

## See also

- Monitor load test scenarios

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: