InfluxDB data source on Grafana Labs

Flux support in Grafana

Sat, 04 Apr 2026 12:26:57 +0000

Flux query language in Grafana

Grafana supports Flux running on InfluxDB 1.8+. See 1.8 compatibility for more information and connection details.

Name	Description
`Name`	The data source name. This is how you refer to the data source in panels and queries. We recommend something like `InfluxDB-Flux`.
`Default`	Default data source means that it will be pre-selected for new panels.
`URL`	The HTTP protocol, IP address and port of your InfluxDB API. InfluxDB 2.0 API port is by default 8086.
`Organization`	The Influx organization that will be used for Flux queries. This is also used to for the `v.organization` query macro.
`Token`	The authentication token used for Flux queries. With Influx 2.0, use the influx authentication token to function. For influx 1.8, the token is `username:password`.
`Default bucket`	(Optional) The Influx bucket that will be used for the `v.defaultBucket` macro in Flux queries.
`Min time interval`	(Optional) Refer to Min time interval.
`Max series`	(Optional) Limits the number of series/tables that Grafana processes. Lower this number to prevent abuse, and increase it if you have lots of small time series and not all are shown. Defaults to 1000.

Min time interval

A lower limit for the auto group by time interval. Recommended to be set to write frequency, for example 1m if your data is written every minute. This option can also be overridden/configured in a dashboard panel under data source options. It’s important to note that this value needs to be formatted as a number followed by a valid time identifier, e.g. 1m (1 minute) or 30s (30 seconds). The following time identifiers are supported:

Identifier	Description
`y`	year
`M`	month
`w`	week
`d`	day
`h`	hour
`m`	minute
`s`	second
`ms`	millisecond

You can use the Flux query and scripting language. Grafana’s Flux query editor is a text editor for raw Flux queries with Macro support.

Supported macros

The macros support copying and pasting from Chronograf.

Macro example	Description
`v.timeRangeStart`	Will be replaced by the start of the currently active time selection. For example, 2020-06-11T13:31:00Z
`v.timeRangeStop`	Will be replaced by the end of the currently active time selection. For example, 2020-06-11T14:31:00Z
`v.windowPeriod`	Will be replaced with an interval string compatible with Flux that corresponds to Grafana’s calculated interval based on the time range of the active time selection. For example, 5s
`v.defaultBucket`	Will be replaced with the data source configuration’s “Default Bucket” setting
`v.organization`	Will be replaced with the data source configuration’s “Organization” setting

For example, the following query will be interpolated as the query that follows it, with interval and time period values changing according to active time selection):

Grafana Flux query:

from(bucket: v.defaultBucket)
  |> range(start: v.timeRangeStart, stop: v.timeRangeStop)
  |> filter(fn: (r) => r["_measurement"] == "cpu" or r["_measurement"] == "swap")
  |> filter(fn: (r) => r["_field"] == "usage_system" or r["_field"] == "free")
  |> aggregateWindow(every: v.windowPeriod, fn: mean)
  |> yield(name: "mean")

Interpolated query send to Influx:

from(bucket: "grafana")
  |> range(start: 2020-06-11T13:59:07Z, stop: 2020-06-11T14:59:07Z)
  |> filter(fn: (r) => r["_measurement"] == "cpu" or r["_measurement"] == "swap")
  |> filter(fn: (r) => r["_field"] == "usage_system" or r["_field"] == "free")
  |> aggregateWindow(every: 2s, fn: mean)
  |> yield(name: "mean")

You can view the interpolated version of a query with the query inspector. For more information, refer to Navigate the Query Inspector.

InfluxDB templates

Sat, 04 Apr 2026 12:26:57 +0000

InfluxDB templates

Instead of hard-coding things like server, application and sensor name in your metric queries you can use variables in their place.

For more information, refer to Templates and variables.

Using variables in InfluxDB queries

There are two syntaxes:

$<varname> Example:

SELECT mean("value") FROM "logins" WHERE "hostname" =~ /^$host$/ AND $timeFilter GROUP BY time($__interval), "hostname"

[[varname]] Example:

SELECT mean("value") FROM "logins" WHERE "hostname" =~ /^[[host]]$/ AND $timeFilter GROUP BY time($__interval), "hostname"

Why two ways? The first syntax is easier to read and write but does not allow you to use a variable in the middle of a word. When the Multi-value or Include all value options are enabled, Grafana converts the labels from plain text to a regex compatible string. Which means you have to use =~ instead of =.

Example dashboard: InfluxDB Templated Dashboard

Query variables

If you add a query template variable, then you can write an InfluxDB exploration (metadata) query. These queries can return things like measurement names, key names or key values. For more information, refer to Add query variable.

For example, you can have a variable that contains all values for tag hostname if you specify a query like this in the query variable Query.

SHOW TAG VALUES WITH KEY = "hostname"

Chained or nested variables

You can also create nested variables, sometimes called chained variables.

For example, if you had another variable, for example region. Then you could have the hosts variable only show hosts from the current selected region with a query like this:

SHOW TAG VALUES WITH KEY = "hostname"  WHERE region = '$region'

You can fetch key names for a given measurement.

SHOW TAG KEYS [FROM <measurement_name>]

If you have a variable with key names you can use this variable in a group by clause. This will allow you to change group by using the variable list at the top of the dashboard.

Ad hoc filters variable

InfluxDB supports the special Ad hoc filters variable type. This variable allows you to specify any number of key/value filters on the fly. These filters are automatically applied to all your InfluxDB queries.

For more information, refer to Add ad hoc filters.

Provision InfluxDB

Sat, 04 Apr 2026 12:26:57 +0000

Provision InfluxDB

You can configure data sources using config files with Grafana’s provisioning system. You can read more about how it works and all the settings you can set for data sources on the provisioning docs page.

Here are some provisioning examples for this data source.

InfluxDB 1.x example

apiVersion: 1

datasources:
  - name: InfluxDB_v1
    type: influxdb
    access: proxy
    database: site
    user: grafana
    url: http://localhost:8086
    jsonData:
      httpMode: GET
    secureJsonData:
      password: grafana

InfluxDB 2.x for Flux example

apiVersion: 1

datasources:
  - name: InfluxDB_v2_Flux
    type: influxdb
    access: proxy
    url: http://localhost:8086
    secureJsonData:
      token: token
    jsonData:
      version: Flux
      organization: organization
      defaultBucket: bucket
      tlsSkipVerify: true

InfluxDB 2.x for InfluxQl example

apiVersion: 1

datasources:
  - name: InfluxDB_v2_InfluxQL
    type: influxdb
    access: proxy
    url: http://localhost:8086
    # This database should be mapped to a bucket
    database: site
    jsonData:
      httpMode: GET
      httpHeaderName1: 'Authorization'
    secureJsonData:
      httpHeaderValue1: 'Token <token>'