Documentation

Select product

Monitor the InfluxData Platform

This page documents an earlier version of . is the latest stable version. View this page in the documentation.

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.

Configure a watcher of watchers system to monitor InfluxDB 1.x servers

How to set up an external InfluxData 1.x TICK stack that monitors another Enterprise or OSS TICK stack.

Considerations for monitoring the 1.x TICK stack

An explanation of internal and external monitoring strategies for your Enterprise or OSS TICK stack with the pros and cons of each.

Set up 1.x monitoring dashboards

Set up dashboards to visualize and monitor the health and performance of your InfluxData 1.x TICK stack.

Tools for monitoring the InfluxData 1.x Platform (TICK stack)

Use the “internal” measurements, SHOW DIAGNOSTICS, and SHOW STATS to monitor your InfluxData Platform.

Was this page helpful?

Thank you for your feedback!

© 2023 InfluxData, Inc.

Where are you running InfluxDB?

Select your InfluxDB Cloud region and cluster or your InfluxDB OSS URL and we’ll customize code examples for you. Identify your InfluxDB Cloud cluster.

  • InfluxDB Cloud
  • InfluxDB OSS or Enterprise
AWS

  • US West (Oregon)

GCP
Azure
Default
Custom

For more information, see InfluxDB Cloud regions or InfluxDB OSS URLs.

Thank you for your feedback!

Let us know what we can do better:

Thank you!

No thanks

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:

State of the InfluxDB Cloud Serverless documentation

InfluxDB Cloud Serverless documentation is a work in progress.

The new documentation for InfluxDB Cloud Serverless is a work in progress. We are adding new information and content almost daily. Thank you for your patience!

If there is specific information you’re looking for, please submit a documentation issue.