Observability support

You can configure OpenText Core Performance Engineering to push observability metrics and data from load test runs to an OpenTelemetry Collector. The observability data can be sent for scripts of all protocols.

In this topic:

Configure an OpenTelemetry Collector

To enable observability support, you need to configure an OpenTelemetry Collector.

To add an OpenTelemetry Collector:

1. On the navigation menu, select Tools and integrations > Streaming accounts > OpenTelemetry server.

2. In the OpenTelemetry Server dialog box, enter the following information.

   Field	Details
   URL	URL of the OpenTelemetry collector, beginning with grpc://.
   Port	Port number of the collector.
   Header	Authorization header to send data to the collector (if required). There are two types: Basic followed by a Base-64 encoded username and password. For example: Basic dXNlcjpwYXNz Bearer followed by a token. For example: Bearer randomtoken1234
   TLS CA certificate	The public key value of the TLS CA certificate to connect to the collector (if required). Note: Not required for non-TLS users.

Back to top

Push data to an OpenTelemetry Collector

Configure load test run data to be pushed to an OpenTelemetry Collector.

To push data to an OpenTelemetry Collector:

1. Prerequisite. An OpenTelemetry Collector must be added to the project. For details, see Configure an OpenTelemetry Collector.

2. Select a test in the Load tests page, and open the Test settings tab .

3. In the Data and logs section, configure the following:

   1. Select the Stream to an OpenTelemetry Collector option.

   2. In Collect data for X % of Vusers, enter the percentage of Vusers whose data should be sent to the collector.

   Note:  

   • Data is sent from at least 1 Vuser. If the specified percentage is equal to less than 1 Vuser in the current test, then data is sent from 1 Vuser.

   • Setting a high percentage may impact load generator performance.

When the load test is run, telemetry data is sent per transaction to the collector. Transactions are tagged with details such as the transaction name, Vuser number, and other information.

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

Back to top

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, enabling you to track the request's flow and correlate related observability data.

Back to top