With this integration, you can export test result metrics from the k6 Cloud to the New Relic's Data Platform to explore your k6 metrics using New Relic.
⭐️ Cloud APM integrations are available on Pro and Enterprise plans, as well as the annual Team plan and Trial.
With New Relic, you can set up a Prometheus remote write instance to collect data. k6 Cloud can export test result metrics to this Prometheus instance to flow data into New Relic.
To set up the New Relic integration on the k6 Cloud, you need the following settings from New Relic:
- License Key
- Prometheus remote write URL
The integration needs a New Relic license key to authenticate and authorize the k6 Cloud for ingesting data.
Once you have the license key, you have to launch a Prometheus instance and set up the remote write integration in New Relic. Follow these instructions.
You have to enable the New Relic integration for each test that you want to export its test result metrics.
Once you have set up the New Relic settings in the test, you can run a cloud test as usual. When running the cloud test, the k6 Cloud will continuously send the test results metrics to New Relic.
Currently, there are two options to set up the Cloud APM settings in the test:
First, you have to configure the New Relic integration for an organization. Click the Cloud APM option on the left sidebar menu under the Manage section, and select New Relic from the list.
In this form, set the URL, license key that you copied previously from New Relic. For more information on the other input fields, see configuration parameters.
Save the New Relic configuration for the current organization.
Note that configuring the New Relic settings for an organization does not enable the integration. You have to enable it manually for each test using the test builder.
Now, create a new test with the test builder or select a test - previously created with the test builder. Click the Cloud APM option on the test builder sidebar to enable the integration for the test.
If you script your k6 tests, you can also configure the Cloud APM settings using the apm option in the k6 script.
The parameters to export the k6 metrics to New Relic are as follows:
|provider(required)||For this integration, the value must be prometheus.|
|remoteWriteURL(required)||URL of the Prometheus remote write endpoint. |
The prometheus_server query param must be included. The license key can optionally be included using the X-License-Key query param.
|credentials||The credentials to authenticate with New Relic. It has a token parameter to set the license key. |
The credentials parameter is optional when the license key is passed via the X-License-Key query param on the remoteWriteURL parameter.
|includeDefaultMetrics||Whether it exports the default APM metrics: data_sent, data_received, http_req_duration, http_reqs, iterations, and vus. Default is true.|
|metrics||List of built-in and custom metrics to export. |
Metric names are validated against the Prometheus metric name conventions—ignoring nonconforming metrics.
|includeTestRunId||Whether all the exported metrics include a test_run_id tag whose value is the k6 Cloud test run id. Default is false. |
Be aware that enabling this setting might increase the cost of your APM provider.
|resampleRate||The rate by which the metrics are resampled and sent to the APM provider in seconds. Default is 3 and acceptable values are integers between 1 and 10.|