Manage analysis servers
This section describes how to configure external analysis database servers to be used with LoadRunner Enterprise.
When you view data online, LoadRunner Enterprise reads it from an internal local time series database installed on the Controller machine. By default, the database stores data from all tests that were run on the Controller for a period of 30 days—you can change the default value in Define host settings. The local database runs as a service to ensure that the data is always available during the run (the service is called LoadRunner Data Service).
You can also install and use an external analysis database which enables you to store data from different runs of the same test run on different Controllers in one centralized location. This helps you perform over-time analytics tasks, and provides the following benefits:
Easy access to live and post-run data.
Enables mashing up LoadRunner Enterprise data with other data vendors, and using third-party dashboards, such as Grafana, to easily visualize the data. For details on the LoadRunner Enterprise—Grafana dashboard, see https://grafana.com/dashboards/7706.
Enables you to use the Quick Trending feature to analyze failed transactions from the Test Runs and Test Management page. For details, see Perform quick trending analysis on test runs.
After you configure an external analysis server, all run data from your selected projects is stored on an external time series database.
When you view data after a test run has finished, LoadRunner Enterprise uses the data stored on the external database. If the external database is unavailable, the data is brought from the local database on the Controller machine.
LoadRunner Enterprise currently supports the InfluxDB time series database for storing data externally.
Note: We recommend using a different connection for different projects in order to keep data access authorization between projects.
To configure your external analysis server, you need to add a connection to your time series database server, and assign it to different projects.
Make sure you have installed and configured InfluxDB on your local machine.
To enable secure communication with your InfluxDB server, you need to add the root certificate to the machine truststore on the LoadRunner Enterprise servers and Controllers. For details, see Distribute certificates in the LoadRunner Enterprise Installation Guide.
In LoadRunner Enterprise Administration, select Configuration > Analysis Servers.
Configure the connection to your time series database.
Click Add new time series database connection, and provide the following details:
The name given to the server.
The database server type.
Enter the fully qualified domain name for the server (IP addresses are not supported).
The port number used by the database server.
A description of the server.
Verify that authorization is enabled in <host installation>\bin\influxdb\influxdb.conf ("auth-enabled = true") otherwise the user and password are skipped.
Database Name. The name of the Influx database server.
User. The user name to access the Influx database server.
Password. The password to access the Influx database server.
Test Connection. Click to test the connection to the database server.
Proxy Server. The name of the proxy server.
User. Enter the relevant user name for the HTTP connection.
Password. Enter the relevant password for the HTTP connection.
Assign the database server to different projects.
In the Linked Projects area, click the Assign Projects button to open the Assign Projects to the Analysis Server dialog box.
Select the projects you want to assign to the server, and click Assign. The selected projects are added to the Linked Projects grid.
You can see project details (the project ID, name, and domain in which the project was created), and add or remove linked projects using the Linked Projects grid.
Automatically upload raw results to the Influx database server
To enable collaboration with other data vendors and viewing the data in third-party dashboards, select Upload results to an external analysis database server (InfluxDB) in Test Options. For details, see Collaborate and export results.
Click Save to save the analysis server template.
Export analysis server details to an Excel file
To export information displayed in the Analysis Servers grid to an Excel file, click . Data from the grid is saved to an Excel file and downloaded to the Downloads folder of the client user.
Notes and limitations
The following are notes and limitations for the analysis server:
Port 8086 should be open for outgoing communication from the LoadRunner Enterprise server, and for incoming communication for the LoadRunner Enterprise host (for an internal database).
For an external database, port 8086 should be open for both incoming and outgoing communication from the LoadRunner Enterpriseserver and LoadRunner Enterprise host.
|Communication security and system user||LoadRunner Enterprise uses the same user name and password as the LoadRunner Enterprise system user to secure the data (IUSR_METRO by default). However, because the internal Influx database server is sensitive to some special characters, we recommend that you avoid using "\" in the password. If a LoadRunner Enterprise system user has a password with "\", you should change it before running any tests on newly-installed hosts.|
|Accessing the internal Influx server after reinstalling host||
Problem: If you uninstall a host and reinstall it again, and during this time the LoadRunner Enterprise system user name or password is changed, access to the internal Influx database on the host will be denied.
This is because InfluxDB stores its data in a folder that also includes the data of the previous authentication user. By default, the folder is under <installation drive>\var (the path is configurable under <host installation>\bin\influxdb\influxdb.conf).
Resolution: You must delete this folder in order for LoadRunner Enterprise to reconfigure the database with the new user. To avoid data loss when deleting this folder, we recommend changing the identity using the InfluxDB REST API.
|Unable to write data||
Problem: If you encounter an "Unable to write data" error, it is possible that the maximum limit of series per database has been reached. The default limit is 1,000,000 transactions per database.