Troubleshoot EDR

EDR 1.0.0

When something looks wrong, start with the symptom quick index. It maps a symptom to the first tool to run and what that tool tells you.

Your situation	Guide
Something looks wrong and you need a starting point	Symptom quick index
The agent won’t start, data isn’t flowing, or lag is climbing	Troubleshoot common EDR issues
The agent crashed or restarted and you have its log	EDR log post-mortem playbook

Before you act on a live metrics or UI reading, cross-check it against edr-inspect state. A metrics snapshot is point-in-time and resets each run, so it can catch a transient at its worst instant. See Data not flowing.

Troubleshoot common EDR issues

Symptom-to-tool quick index, agent startup errors, halted-state recovery, replication lag, and Docker-specific troubleshooting for EDR.

EDR log post-mortem playbook

Diagnose what happened to a crashed or restarted EDR agent from a captured log, using structured JSON log fields and a deterministic procedure.

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 3 Enterprise and this documentation. To find support, use the following resources:

Customers with an annual or support contract can contact InfluxData Support. Customers using a trial license can email trial@influxdata.com for assistance.

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

Explorer 1.11 is now available

Six new visualization types, plus password and SSO sign-in and user management for InfluxDB 3 Enterprise.

Password and SSO sign-in with role-based access.
Manage Users page under a new Security section.
New visualizations: Area, Single Stat, Gauge, Pie, Scatter, and Ranking.
EXPLAIN and EXPLAIN ANALYZE in the SQL editor.

Explorer 1.11 release notes

InfluxDB 3.12 is now available

Back up your catalog before you upgrade. Rolling back to 3.11.x requires restoring that backup.

Add columns to existing tables with influxdb3 update table.
Faster queries and startup with DataFusion 52.5.
New defaults: finite --max-concurrent-queries and an enforced WAL buffer limit.

Upgrade guide | Release notes | Announcement

InfluxDB 3 Enterprise 3.12 is now available

Back up your catalog before you upgrade. Rolling back to 3.11.x requires restoring that backup.

Faster bulk import, including from object storage.
Distributed compaction (beta).
Schema enforcement per database.
User authentication and RBAC are generally available.

Upgrade guide | Release notes | Announcement

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