Replace a legacy In-Memory Only datasource
Mode: Configuration: Datasources is shown in Expert mode (sidebar footer toggle Mode: Basic / Expert).
Overview
Older versions of the LoadGen Platform offered In-Memory Only as a backend for a Testing datasource. That backend stores nothing: every result is discarded as it arrives, and Analyse has nothing to read afterwards. A load test that writes to it runs normally and then leaves no results behind.
In-Memory Only can no longer be chosen. The Add dialog on the Testing tab offers InfluxDB, SQL Server and CSV, and the API refuses to save a datasource with the In-Memory Only backend. A datasource that was created with it before keeps working as it did, and is marked as legacy so you can find it and move it to a backend that keeps your results.
This guide finds those datasources and switches them to a real backend.
Before you begin
- You need a role that can change datasources. A read-only role can open the page but not save.
- Have the connection details of the backend you will move to ready: for InfluxDB its internal URL and API token, for SQL Server its connection details, for CSV the location the appliance writes to. Configure datasources describes each backend's fields.
- Results that were sent to an In-Memory Only datasource were never stored, so there is nothing to migrate. Only runs after the switch keep their results.
Steps
Step 1
Open CONFIGURATION > Datasources and select the Testing tab. The info card at the top reads "Backends: InfluxDB, SQL Server, CSV" and "Datasource is selected per load profile".
Step 2
Look through the Backend column. A datasource that still uses the old backend shows its backend type with an amber Legacy badge next to it. If no row carries the badge, nothing on this appliance uses In-Memory Only and you are done.
Step 3
Open the legacy datasource for editing. The Edit Datasource: Testing dialog opens with an amber notice:
In-Memory Only (legacy): This backend stores no data at all: results are discarded as they arrive and Analyse cannot read them. It can no longer be saved. Choose another backend to keep this datasource.
Step 4
Keep the Datasource Name as it is, so every load profile that points at this datasource follows the change. Under Backend Type, choose InfluxDB, SQL Server or CSV, and fill in that backend's connection fields.
Step 5
Save the dialog. The row now shows the new backend and the Legacy badge is gone.
If you save without choosing another backend, the save is refused with a message that starts "Failed to save: Validation failed." and explains that the In-Memory Only backend stores no data. Nothing is changed; choose another backend and save again.
Verify the result
Run a short load test with a load profile that uses this datasource, then open the run in Analyse. Results that appear there are being stored by the new backend.
Notes
- You can also delete a legacy datasource instead of switching it. Point the load profiles that used it at another Testing datasource first: a datasource is selected per load profile.
- A new Testing datasource cannot be created with In-Memory Only at all; the backend is not offered in the Add Testing Datasource dialog.