Documentation

Get started with the InfluxData Platform

To get started with the InfluxDB 2.0 platform, see InfluxDB Cloud or InfluxDB OSS 2.0.

To get started with the InfluxData 1.x platform, download and install each component of the TICK stack, or Install the InfluxData Sandbox, and then follow the steps below.

Getting started setup

Understand how Telegraf writes data to InfluxDB

Once Telegraf is installed and started, it will send system metrics to InfluxDB by default, which automatically creates a ‘telegraf’ database.

The configuration file for Telegraf specifies where metrics come from and where they go (inputs and outputs). In this example, we’ll focus on CPU data, which is one of the default system metrics generated by Telegraf. For this example, it is worth noting some relevant values:

  • [agent].interval - declares the frequency at which system metrics will be sent to InfluxDB.
  • [[outputs.influxdb]] - declares how to connect to InfluxDB and the destination database, which is the default ‘telegraf’ database.
  • [[inputs.cpu]] - declares how to collect the system cpu metrics to be sent to InfluxDB. Enabled by default.

For details about the configuration file, see Get started with Telegraf.

Query data in InfluxDB

As reviewed above, Telegraf is sending system data, including CPU usage, to InfluxDB. There are two ways you can query your InfluxDB data:

Query example:

SELECT "usage_system",
       "usage_user"
FROM "telegraf"."autogen"."cpu"
WHERE time > now() - 30m

Visualize that data in a Chronograf dashboard

Now that you’ve explored your data with queries, you can build a dashboard in Chronograf to visualize the data. For details, see Create a dashboard and Using pre-created dashboards.

Create an alert in Kapacitor based on that data

Since InfluxDB is running on localhost:8086, Kapacitor finds it during start up and creates several subscriptions on InfluxDB. These subscriptions tell InfluxDB to send all the data it receives from Telegraf to Kapacitor.

For step-by-step instructions on how to set up an alert in Kapacitor based on your data, see Creating Chronograf alert rules.


Was this page helpful?

Thank you for your feedback!


Introducing InfluxDB Clustered

A highly available InfluxDB 3.0 cluster on your own infrastructure.

InfluxDB Clustered is a highly available InfluxDB 3.0 cluster built for high write and query workloads on your own infrastructure.

InfluxDB Clustered is currently in limited availability and is only available to a limited group of InfluxData customers. If interested in being part of the limited access group, please contact the InfluxData Sales team.

Learn more
Contact InfluxData Sales

The future of Flux

Flux is going into maintenance mode. You can continue using it as you currently are without any changes to your code.

Flux is going into maintenance mode and will not be supported in InfluxDB 3.0. This was a decision based on the broad demand for SQL and the continued growth and adoption of InfluxQL. We are continuing to support Flux for users in 1.x and 2.x so you can continue using it with no changes to your code. If you are interested in transitioning to InfluxDB 3.0 and want to future-proof your code, we suggest using InfluxQL.

For information about the future of Flux, see the following: