Using InfluxDB in Grafana

• Open the side menu by clicking the Grafana icon in the top header.
• In the side menu under the link you should find a link named Data Sources.
• Click the + Add data source button in the top header.
• Select InfluxDB from the Type dropdown.

Access mode controls how requests to the data source will be handled. Server should be the preferred way if nothing else stated.

All requests will be made from the browser to Grafana backend/server which in turn will forward the requests to the data source and by that circumvent possible Cross-Origin Resource Sharing (CORS) requirements. The URL needs to be accessible from the grafana backend/server if you select this access mode.

Browser access mode

All requests will be made from the browser directly to the data source and may be subject to Cross-Origin Resource Sharing (CORS) requirements. The URL needs to be accessible from the browser if you select this access mode.

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:

Query Editor

[

]()

You find the InfluxDB editor in the metrics tab in Graph or Singlestat panel’s edit mode. You enter edit mode by clicking the panel title, then edit. The editor allows you to select metrics and tags.

Filter data (WHERE)

To add a tag filter click the plus icon to the right of the WHERE condition. You can remove tag filters by clicking on the tag key and select —remove tag filter—.

Regex matching

You can type in regex patterns for metric names or tag filter values, be sure to wrap the regex pattern in forward slashes (). Grafana will automatically adjust the filter tag condition to use the InfluxDB regex match condition operator (=~).

In the SELECT row you can specify what fields and functions you want to use. If you have a group by time you need an aggregation function. Some functions like derivative require an aggregation function. The editor tries simplify and unify this part of the query. For example:

The above will generate the following InfluxDB SELECT clause:

Select multiple fields

Use the plus button and select Field > field to add another SELECT clause. You can also specify an asterix * to select all fields.

Group By

Text Editor Mode (RAW)

You can switch to raw query mode by clicking hamburger icon and then Switch editor mode.

Alias patterns

• $m = replaced with measurement name
• $measurement = replaced with measurement name
• $col = replaced with column name
• $tagexampletag = replaced with the value of the exampletag tag. The syntax is $tag_yourTagName (must start with $tag). To use your tag as an alias in the ALIAS BY field then the tag must be used to group by in the query.

You can remove the group by time by clicking on the time part and then the x icon. You can change the option Format As to Table if you want to show raw data in the Table panel.

Querying and displaying log data from InfluxDB is available via .

Select the InfluxDB data source, change to Logs using the Metrics/Logs switcher, and then use the Measurements/Fields button to display your logs.

Log Queries

The Logs Explorer (the Measurements/Fields button) next to the query field shows a list of measurements and fields. Choose the desired measurement that contains your log data and then choose which field Explore should use to display the log message.

Once the result is returned, the log panel shows a list of log rows and a bar chart where the x-axis shows the time and the y-axis shows the frequency/count.

Filter search

To add a filter click the plus icon to the right of the Measurements/Fields button or a condition. You can remove tag filters by clicking on the first select and choosing —remove filter—.

Templating

Instead of hard-coding things like server, application and sensor name in you metric queries you can use variables in their place. Variables are shown as dropdown select boxes at the top of the dashboard. These dropdowns makes it easy to change the data being displayed in your dashboard.

Checkout the documentation for an introduction to the templating feature and the different types of template variables.

Query variable

If you add a template variable of the type you can write a InfluxDB exploration (meta data) query. These queries can return things like measurement names, key names or key values.

SHOW TAG VALUES WITH KEY = "hostname"

You can also create nested 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:

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 dropdown at the top of the dashboard.

There are two syntaxes:

$<varname> Example:

[[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:

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 will automatically be applied to all your InfluxDB queries.

allows you to overlay rich event information on top of graphs. You add annotation queries via the Dashboard menu / Annotations view.

An example query:

For InfluxDB you need to enter a query like in the above example. You need to have the where $timeFilter part. If you only select one column you will not need to enter anything in the column mapping fields. The Tags field can be a comma separated string.

Configure the Datasource with Provisioning

It’s now possible to configure datasources using config files with Grafana’s provisioning system. You can read more about how it works and all the settings you can set for datasources on the

Here are some provisioning examples for this datasource.

apiVersion: 1
datasources:
  - name: InfluxDB
    type: influxdb
    access: proxy
    database: site
    user: grafana
    password: grafana
    url: http://localhost:8086
    jsonData: