Documentation

Select product

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.

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!

© 2025 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

New in InfluxDB 3.5

Key enhancements in InfluxDB 3.5 and the InfluxDB 3 Explorer 1.3.

See the Blog Post

InfluxDB 3.5 is now available for both Core and Enterprise, introducing custom plugin repository support, enhanced operational visibility with queryable CLI parameters and manual node management, stronger security controls, and general performance improvements.

InfluxDB 3 Explorer 1.3 brings powerful new capabilities including Dashboards (beta) for saving and organizing your favorite queries, and cache querying for instant access to Last Value and Distinct Value caches—making Explorer a more comprehensive workspace for time series monitoring and analysis.

For more information, check out:

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On November 3, 2025, the latest tag for InfluxDB Docker images will point to InfluxDB 3 Core. To avoid unexpected upgrades, use specific version tags in your Docker deployments.

If using Docker to install and run InfluxDB, the latest tag will point to InfluxDB 3 Core. To avoid unexpected upgrades, use specific version tags in your Docker deployments. For example, if using Docker to run InfluxDB v2, replace the latest version tag with a specific version tag in your Docker pull command–for example:

docker pull influxdb:2