Monitor InfluxDB Enterprise v1

Monitoring is the act of observing changes in data over time. “Monitoring” covers two different things:

Monitor InfluxDB itself—track the health and performance of your InfluxDB Enterprise cluster.
Monitor other systems with InfluxDB—use InfluxDB and the wider TICK stack (Telegraf, Chronograf, Kapacitor) as your monitoring backend for infrastructure and applications.

Monitor with InfluxDB Insights

For InfluxDB Enterprise customers, Insights is a free service that monitors your cluster and sends metrics to a private Cloud account. This allows InfluxDB Support to monitor your cluster health and access usage statistics when assisting with support tickets that you raise.

To apply for this service, please contact InfluxData support.

Monitor InfluxDB itself

Monitor other systems with InfluxDB

Monitor Kubernetes

Was this page helpful?

Thank you for your feedback!

Support and feedback

Thank you for being part of our community! We welcome and encourage your feedback and bug reports for InfluxDB Enterprise v1 and this documentation. To find support, use the following resources:

Customers with an annual or support contract can contact InfluxData Support.

Edit this page Submit docs issue

© 2026 InfluxData, Inc.

InfluxDB OSS 2.9.0: API tokens are hashed by default

Stronger token security in InfluxDB OSS 2.9.0 — tokens are hashed on disk by default. Existing tokens are hashed on first startup and can’t be recovered afterward. Capture any plaintext tokens you still need before you upgrade.

View InfluxDB OSS 2.9.0 release notes

Hashed tokens authenticate exactly like unhashed tokens — clients and integrations keep working.

Also new in 2.9.0:

Configurable backup compression
Restore support for backups containing hashed tokens
Tighter Edge Data Replication queue validation
Flux upgrade
Compaction reliability improvements

Key enhancements in Explorer 1.9

Explorer 1.9 is now available with InfluxQL support, an AI-assisted Flux to SQL converter (beta), and new live sample data simulators.

View Explorer 1.9 release notes

Explorer 1.9 includes new features and improvements that make it easier to query, visualize, and manage data.

Highlights:

Flux to SQL converter (beta): Convert Flux queries to SQL with an AI-assisted converter.
InfluxQL support: Query data with InfluxQL in the Data Explorer and dashboards, and save and load InfluxQL queries.
InfluxQL visualizations: Render line and bar charts from InfluxQL results with per-tag series grouping.
Query error history: Review a history of query errors in the query tool.
Live sample data simulators: Generate continuous live sample data with new bird data and signal generator simulators.

For more details, see Explorer 1.9 release notes

InfluxDB 3.11 is now available

InfluxDB 3 Core 3.11 improves processing engine trigger reliability and adds a configurable graceful shutdown.

Key updates in InfluxDB 3 Core 3.11:

Processing engine trigger reliability improvements—capped async trigger concurrency, bounded retries for failed triggers, and WAL triggers that skip empty flushes.
Configurable graceful shutdown with the new --shutdown-timeout option.
Read the announcement
InfluxDB 3 Core release notes

InfluxDB 3 Enterprise 3.11: A significant performance upgrade for complex time series workloads

Performance and flexibility for heavier, more complex workloads.

Key updates in InfluxDB 3 Enterprise 3.11:

Upgraded storage engine reaches general availability. New clusters default to Parquet; upgrade with --upgrade-pacha-tree.
In-place and incremental backup and restore.
Integrated Explorer UI—run with --mode all,webui.
Bulk import: import from remote object store sources (for example, S3) with configurable concurrency.
Compaction and query performance improvements.
Catalog migration—back up your catalog before upgrading.
Read the announcement
InfluxDB 3 Enterprise release notes

Telegraf Controller 1.1 now available

Telegraf Controller 1.1 adds high availability (Telegraf Enterprise), global constants, configuration groups, configuration aliases, and configuration versioning.

Telegraf Controller 1.1 lets teams make fleet-wide configuration changes with a single edit using global constants, configuration groups, and configuration aliases. Configuration versioning makes every change traceable, comparable, and reversible. High availability, available with Telegraf Enterprise, automatically fails over between Controller instances so agents can continue pulling configurations and reporting health if an instance goes down.

InfluxDB OSS 1.13.0 is now available

InfluxDB OSS 1.13.0 adds mTLS support, adaptive TSI cache sizing, and a hardening option to mitigate SSRF.

View InfluxDB OSS 1.13.0 release notes

Key updates in InfluxDB OSS 1.13.0:

mTLS support for the HTTP, OpenTSDB, and subscriber services.
Adaptive TSI cache sizing—the series ID set cache can grow and shrink based on measured query hit rate.
hardening-enabled option to mitigate server-side request forgery (SSRF) in Flux HTTP requests.

For details, see the InfluxDB OSS 1.13.0 release notes.

InfluxDB Enterprise 1.13.0 is now available

InfluxDB Enterprise 1.13.0 adds mTLS support and changes the default replication factor from 3 to 2.

View InfluxDB Enterprise 1.13.0 release notes

Key updates in InfluxDB Enterprise 1.13.0:

Default replication factor changed to 2 (previously 3) for new databases and retention policies. Existing ones aren’t affected.
mTLS support for Enterprise data and meta nodes.
All InfluxDB OSS 1.13.0 updates apply to Enterprise too.

For details, see the InfluxDB Enterprise 1.13.0 release notes.

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On September 15, 2026, 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