To install the LoadRunnerEnterprise provider, create a YAML file (called provider.yml in this example) with the definition of the provider:

Then you can install the provider using the Akamas CLI:

The installed provider is shared with all users of your Akamas installation and can monitor many different systems, by configuring appropriate telemetry provider instances.

The LoadRunner Enterprise provider collects metrics from a LoadRunner Enterprise instance and makes them available to Akamas.

Prerequisites

This section provides the minimum requirements that you should match before using the LoadRunnerEnterprise telemetry provider.

Supported versions

• LoadRunner Enterprise 12.60, 12.63 and 2020 SP3, 2022 and 2022 R1

• InfluxDB 1.7 and 1.8

Network requirements

• Port 8086 between Akamas VM to InfluxDB host, opened in both directions. This port is used to gather metrics.

Permissions

• The provider requires a user that can access InfluxDB.

• The user must have read permission on the database containing the LoadRunner metrics.

Supported component types

• Web Application

You can check LoadRunner provider metrics mapping to see how component-types metrics are extracted by this provider.

Workflow requirements

This section lists the workflow operators this provider depends on.

• LoadRunnerEnterprise operator

Setup the data source

To set up the integration between Loadrunner Enterprise and InfluxDB please follow the official Microfocus documentation. Akamas does not require any additional setup on the data source.

Components configuration

Akamas reasons in terms of a system to be optimized and in terms of parameters and metrics of components of that system. To understand the link between metrics collected from LoadRunnerEnterprise through InfluxDB and a specific component, the LoadRunnerEnterprise provider looks up some properties in the components of a system:

• loadrunnerenterprise

You can use this example to start building your component specification:

# Specification for a component, whose metrics should be collected by the Prometheus Provider
name: "WebApp1" # name of the component
description: "WebApp for payment services" # description of the component
properties:
  loadrunnerenterprise: ""

Create a telemetry instance

To create an instance of the LoadRunnerEnterprise provider, build a YAML file (instance.yml in this example) with the definition of the instance:

#LoadRunnerEnterprise Telemetry Provider Instance
provider: LoadRunnerEnterprise
config:
 address: http://influxdb.mycompany.com
 port: 8086
 username: akamas
 password: influxdbpassword
 database: pc_akamas_project

Then you can create the instance using the Akamas CLI:

akamas create telemetry-instance instance.yml

Configuration options

When you create an instance of the LoadRunnerEnterprise provider, you should specify some configuration information to allow the provider to correctly extract and process metrics from Prometheus.

You can specify configuration information within the config part of the YAML of the instance definition.

Required properties

• address: The address of the InfluxDB instance, in the form of schema://address (i.e https://influxdb.mycompay.com)

• port: The InfluxDB port

• username: The username required to connect to InfluxDB.

• password: The password for the username

• database: The database name where LoadRunner metrics are stored

Telemetry instance reference

provider: LoadRunnerEnterprise # the instance of the LoadRunnerEnterprise provider
config:
 address: https://influxdb.mycompany.com # the address of the Prometheus instance
 port: 8086 # the port of the Prometheus
 username: akamasforinflux
 passowrd: influxpassword
 database: pc_akamas_project
 verifySSL: false
 transactions:
   - mytransaction1
   - mytransaciton2

This table reports the reference for the config section within the definition of the LoadRunnerEnterprise provider instance:

Exported metrics

users
transactions_throughput
transactions_response_time
transactions_response_time_min
transactions_response_time_max
requests_throughput
requests_error_throughput