StresStimulus can send real-time results to an InfluxDB time-series database during a load test. Then, the data can be visually displayed in a graphical dashboard, such as Graphana and Sumo Logic.
Write frequency
The data write frequency to the InfluxDB database is controlled by the Graph sample rate property described here.
Configuring the connection to InfluxDB
- Select the InfluxDB connection options property in the Result Storage node and click the ... button.
- In the InfluxDB settings dialog box, check the Enable InfluxDB checkbox.
- Enter the URL of the InfluxDB server
- The security token
- Organization
- The default bucket
- Click the Test Connection... button to test the connection to the InfluxDB server
- Click OK to save the connection settings
Saved metrics
All saved StresStimulus datapoints will have a measurement name: stresstimulus
Raw metrics:
| Field | Description |
|---|---|
| raw.users | The number of instantiated and active VUs, iterating through their respective test objects. |
| raw.iterationsStarted | The number of iterations started by the test object |
| raw.iterationsSuccess | The number of iterations completed successfully by the test object |
| raw.iterationsFail | The number of iterations that failed by the test object |
| raw.requestCount | The total number of requests issued by all the VUs executing their test object |
| raw.responseSuccess | The total number of successful (non-error or non-timeout) responses received by all the VUs |
| raw.responseFail | The total number of failed (error or timeout) responses received by all the VUs |
| raw.requestBytes | The total number of bytes sent during the test |
| raw.responseBytes | The total number of bytes received during the test |
KPI metrics:
| Field | Description |
|---|---|
| kpi.requestsPerSec | The number of requests being sent per second. Calculated by taking the number of requests from the previous sample timestamp and dividing by the sample rate. |
| kpi.avgResponse | The average response time of the sent requests. This is the average value since the previous sample timestamp. The data point is skipped to reflect an accurate response time curve if no responses have been received since the previous sample timestamp. |
| kpi.kbPerSec | The number of kilobytes currently received per second. Calculated by taking the total payload downloaded from the previous sample timestamp and dividing it by the sample rate. |
| kpi.errorsPerSec | The number of errors currently received per second. Calculated by taking the number of request errors from the previous sample timestamp and dividing it by the sample rate. |
| kpi.pendingRequests | The number of currently pending requests. Pending requests are issued, but StresStimulus has not yet received a response. Generally, a higher number of pending requests indicates a slower server response. This parameter can be used to gauge performance change in several test runs. |
| kpi.transactionsPerSec | The total number of transactions completed per second. A completed transaction executes all child objects. If transactions are nested, each transaction is counted separately toward the total completed transactions. |
Transaction metrics:
Every transaction will have a corresponding metric. The metric will measure the average response time of every transaction.
The following naming convention is used: transaction.{testCaseName}.{transactionName}.
Overview
Content Tools
