The LoadRunner provider collects metrics generated by a LoadRunner instance (converted to their JSON format and placed in CIFS network share) and makes them available to Akamas.
Prerequisites
This section provides the minimum requirements that you should match before using the LoadRunner telemetry provider.
Micro Focus LoadRunner 12.60 or 2020
The network share is reachable at port 445/TCP
The network share is reachable at port 139/UDP
Username, domain (if required), and password of the network share.
Read permission on the network share.
Web Application
You can check LoadRunner provider metrics mapping to see how component-types metrics are extracted by this provider.
The provider expects that its required data are on a CIFS share. If you are using the LoadRunner operator, please follow the instruction on here below on how to export LoadRunner results in a network share by setup a share on the LoadRunner Controller.
To share a folder on Windows, please follow these steps:
Right-click on the folder, then select Properties
Go to Sharing tab, then select Advanced Sharing
In the opened window, enable Share this folder
In the "Share name" textbox type the name of the share. This is the name of the share over the network\
Then click on Permissions, then Add
In the textbox type the name of the user or the group (with the domain if required) that you want to grant access to the share, then click "OK"\
Select the added user (or group) and grant the required permissions\
Click OK, OK, and then Close
Open "This PC" from the Start menu, then click on "Map network drive"\
In the "Map Network Drive" window, select a suitable drive letter name and enter the remote folder path of the network share that has been given to you by your storage admin (it should be something with the format \\mycompanyshareserver.mycompany\foldername)\
Make sure to check "Reconnect at sign-in" and "Connect using different credentials".
Click Finish
In the "Windows Security" window enter the username (with the domain, if required) and the password for the network share and check "Remember my credentials".
Click "OK"
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 LoadRunner and a specific component, the LoadRunner provider looks up the property loadrunner
in the components of a system:
To install the LoadRunner 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.
To create an instance of the LoadRunner provider, build a YAML file (instance.yml
in this example) with the definition of the instance:
Then you can create the instance for the system
using the Akamas CLI:
When you create an instance of the LoadRunner provider, you should specify some configuration information to allow the provider to correctly extract and process metrics from LoadRunner.
You can specify configuration information within the config
part of the YAML of the instance definition.
hostname
: The hostname or IP of the server that hosts the CIFS share where the LoadRunner results have been exported. See .
username
: The username and the domain required to access the network share. Supported formats are:
username
domain\username
username@domain
password
: The password required to access the network share
shareName
: The name of the network share as it is exposed by the server
The following YAML file provides the reference for the definition of a telemetry instance.
The following table describes the reference for the config
section within the definition of the LoadRunner provider instance:
Field | Type | Description | Default Value | Restrictions | Required |
---|
hostname | String | - | IP address or FQDN | Yes |
username | String | The username and the domain required to access the share | - | Supported formats:
| Yes |
password | String | The password required to access the share | - | - | Yes |
shareName | String | The name of the share as it is exposed by the server | - | - | Yes |
resultFolder | String | The name of the folder where to look for test results. The final path is {pathPrefix}{resultsFolder}. The default path is | {studyName}\{experimentId}\{trialId} | A valid Windows path segment, might contain the placeholders: {studyName}, {experimentId}, {trialId} | No |
pathPrefix | String | A prefix the for path where to look for test results. | - | A valid Windows path | No |
the hostname or IP of the server that hosts the CIFS share where the LoadRunner results have been exported. See
See