The LoadRunner Enterprise provider collects metrics from a LoadRunner Enterprise instance and makes them available to Akamas.
This section provides the minimum requirements that you should match before using the LoadRunnerEnterprise telemetry provider.
LoadRunner Enterprise 12.60, 12.63 and 2020 SP3, 2022 and 2022 R1
InfluxDB 1.7 and 1.8
Port 8086 between Akamas VM to InfluxDB host, opened in both directions. This port is used to gather metrics.
The provider requires a user that can access InfluxDB.
The user must have read permission on the database containing the LoadRunner metrics.
Web Application
You can check LoadRunner provider metrics mapping to see how component-types metrics are extracted by this provider.
This section lists the workflow operators this provider depends on.
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.
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:
To create an instance of the LoadRunnerEnterprise provider, build a YAML file (instance.yml
in this example) with the definition of the instance:
Then you can create the instance using the Akamas CLI:
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.
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
This table reports the reference for the config
section within the definition of the LoadRunnerEnterprise provider instance:
Field | Type | Description | Default value | Restrictions | Required |
---|
address | String | The address of the InfluxDB | - | A valid URL | Yes |
port | Integer | The port of the InfluxDB | - | A valid port | yes |
username | String | The username to connect to InfluxDB | - | - | Yes |
password | String | The password of the specified user | - | - | Yes |
database | String | The database with the metrics | - | - | Yes |
verifySSL | Boolean | Wheter to check the certificate, of InfluxDB API is exposed in HTTPS | false | true/false | No |
transactions | List of string | Restrict metrics collection to the listed transactions names. If not specified the provider will collect metrics of all transactions | Empty |
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.