--- title: "InfluxDB | Grafana k6 documentation" description: "k6 has built-in support for InfluxDB v1, and provides an output extension to store k6 metrics in InfluxDB v2. This document shows you how to configure this integration." --- > For a curated documentation index, see [llms.txt](/llms.txt). For the complete documentation index, see [llms-full.txt](/llms-full.txt). # InfluxDB k6 supports sending output metrics to InfluxDB v1.0 and v2.0. ## Send k6 metrics to InfluxDB v1.0 k6 has built-in support to send metrics to InfluxDB v1.0. You can use the `--out` flag with the `influxdb` option: Bash ![Copy code to clipboard](/media/images/icons/icon-copy-small-2.svg) Copy ```bash k6 run --out influxdb=http://localhost:8086/myk6db script.js ``` The example command makes k6 connect to a local InfluxDB instance and send the results from the test to a database named `myk6db`. If the database doesn’t exist, k6 creates one automatically. ### Use a URL path prefix A reverse proxy can expose several InfluxDB instances under one hostname, using a different path prefix for each instance. Include that prefix before the database name to send metrics to the correct instance with the built-in InfluxDB v1 output: sh ![Copy code to clipboard](/media/images/icons/icon-copy-small-2.svg) Copy ```sh k6 run --out influxdb=https://influxdb.example.com/influxdb/myk6db script.js ``` Replace `https://influxdb.example.com/influxdb` with your InfluxDB address and path prefix, `myk6db` with your database name, and `script.js` with your test script. k6 uses the final URL path segment as the database name and preserves the preceding path as the address prefix. In this example, k6 sends metrics to `/influxdb/write` for the `myk6db` database. A trailing slash means that the entire path is the prefix and the URL does not specify a database name. For example, `https://influxdb.example.com/influxdb/` uses `/influxdb` as the prefix and keeps the database configured through other options, or the default `k6` database. ## Send k6 metrics to InfluxDB v2.0 Using the [InfluxDB extension](https://github.com/grafana/xk6-output-influxdb), you can store k6 metrics in [InfluxDB v2.0](https://docs.influxdata.com/influxdb/v2.0/) and analyze your performance results with Grafana or [other tools](https://docs.influxdata.com/influxdb/cloud-serverless/query-data/tools/). ### Build the k6 version To build a k6 binary with the extension, first, make sure you have [Go](https://golang.org/doc/install) and [Git](https://git-scm.com/) installed on your machine. Then, open your terminal and run the following commands: Bash ![Copy code to clipboard](/media/images/icons/icon-copy-small-2.svg) Copy ```bash # Install xk6 go install go.k6.io/xk6/cmd/xk6@latest # Build the k6 binary xk6 build --with github.com/grafana/xk6-output-influxdb ... [INFO] Build environment ready ... [INFO] Building k6 ... [INFO] Build complete: ./k6 ``` xk6 will create the new k6 binary in the local folder. > Note > > To learn more about how to build custom k6 versions, check out [xk6](https://github.com/grafana/xk6). ### Run the test Check that the InfluxDB instance to store the k6 metrics is running. Use the previous k6 binary and run the test passing the following [options](#options): Bash ![Copy code to clipboard](/media/images/icons/icon-copy-small-2.svg) Copy ```bash K6_INFLUXDB_ORGANIZATION="" \ K6_INFLUXDB_BUCKET="" \ K6_INFLUXDB_TOKEN="" \ K6_INFLUXDB_ADDR="" \ ./k6 run script.js -o xk6-influxdb ``` k6 runs the test script and sends the [k6 metrics](/docs/k6/v2.3.x/using-k6/metrics/) in real-time to the InfluxDB instance. You can now select the bucket to [query](https://docs.influxdata.com/influxdb/v2.7/query-data/) and [visualize](https://docs.influxdata.com/influxdb/v2.7/visualize-data/) the stored k6 metrics, for example, using the [InfluxDB Data Explorer](https://docs.influxdata.com/influxdb/v2.7/query-data/execute-queries/data-explorer/). ### Options Here is the full list of options that can be configured and passed to the extension: Expand table | ENV | Default | Description | |----------------------------------|-----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | K6\_INFLUXDB\_ORGANIZATION | | Your InfluxDB organization name. [View organizations](https://docs.influxdata.com/influxdb/v2.7/organizations/). | | K6\_INFLUXDB\_BUCKET | | The bucket name to store k6 metrics data. [Manage buckets](https://docs.influxdata.com/influxdb/v2.7/organizations/buckets/). | | K6\_INFLUXDB\_TOKEN | | An API token that provides authorized access to store data. [Manage API tokens](https://docs.influxdata.com/influxdb/v2.7/security/tokens/). | | K6\_INFLUXDB\_ADDR | http://localhost:8086 | The address of the InfluxDB instance. | | K6\_INFLUXDB\_PUSH\_INTERVAL | 1s | The flush’s frequency of the `k6` metrics. | | K6\_INFLUXDB\_CONCURRENT\_WRITES | 4 | Number of concurrent requests for flushing data. It is useful when a request takes more than the expected time (more than flush interval). | | K6\_INFLUXDB\_TAGS\_AS\_FIELDS | vu:int,iter:int,url | A comma-separated string to set `k6` metrics as non-indexable fields (instead of tags). An optional type can be specified using :type as in vu:int will make the field integer. The possible field types are int, bool, float and string, which is the default. Example: vu:int,iter:int,url:string,event\_time:int. | | K6\_INFLUXDB\_INSECURE | false | When `true`, it will skip `https` certificate verification. | | K6\_INFLUXDB\_PRECISION | 1ns | The timestamp [Precision](https://docs.influxdata.com/influxdb/v2.7/reference/glossary/#precision). | | K6\_INFLUXDB\_HTTP\_PROXY | | Sets an HTTP proxy for the InfluxDB output. | ### Grafana Dashboards You can use Grafana to query and visualize data from an InfluxDB instance. The instructions are available on [InfluxDB](https://docs.influxdata.com/influxdb/v2.7/tools/grafana/) and [Grafana](/docs/grafana/latest/datasources/influxdb/). You can also build a [custom Grafana dashboard](/docs/k6/v2.3.x/results-output/grafana-dashboards/) to visualize the testing results in your own way. For testing purposes, the [InfluxDB extension](https://github.com/grafana/xk6-output-influxdb) repository includes a [docker-compose setup](https://github.com/grafana/xk6-output-influxdb#docker-compose) with two basic dashboards.