Documentation

Install the InfluxData 1.x TICK stack (OSS)

Download the TICK stack components

To download each of the TICK stack components, see InfluxData downloads page. Telegraf, InfluxDB, Chronograf, and Kapacitor are each separate binaries that need to be installed, configured, and started separately.

Install Telegraf

The Telegraf installation instructions walk through installing and configuring Telegraf.

Install InfluxDB

The InfluxDB OSS installation instructions walk through installing and configuring the open source version of InfluxDB.

Install Chronograf

The Chronograf installation instructions walk through installing and configuring Chronograf.

Install Kapacitor

The Kapacitor OSS installation instructions walk through installing and configuring the open source version of Kapacitor.

InfluxData Sandbox

The InfluxData Sandbox is an alternative method for installing the OSS TICK stack that uses Docker and Docker Compose to build and network each component. For information about installing the Sandbox, view the InfluxData Sandbox installation instructions.


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: