Monitor the InfluxData Platform

One of the primary use cases for the InfluxData Platform is as server and infrastructure monitoring solution. No matter what type of data you’re using the platform to collect and store, it’s important to monitor the health of your stack and identify any potential issues.

To monitor the InfluxDB 2.0 platform, see Monitor InfluxDB 2.0.

To monitor the InfluxData 1.x platform, see the following pages for information about setting up a 1.x TICK stack that monitors another OSS or Enterprise TICK stack. They cover different potential monitoring strategies and visualizing the monitoring data in a way that makes it easy to recognize, alert on, and address anomalies as they happen.

Leverage InfluxDB Cloud and pre-built InfluxDB templates to monitoring your InfluxDB setup. Start using InfluxDB Cloud at no cost with the Free Plan. Use it as much and as long as you like within the plan’s rate-limits. Limits are designed to let you monitor 5-10 sensors, stacks or servers comfortably. Monitoring a single InfluxDB OSS instance or even a modest InfluxDB Enterprise cluster should easily fit within the free plan limits. If you exceed the plan limits because of high resolution data or longer data retention, upgrade to the Usage-Based Plan.

Start monitoring your InfluxDB instance by signing up for an InfluxDB Cloud account.

Was this page helpful?

Thank you for your feedback!

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: