Image
close
Documentation

Kapacitor

InfluxDB 3

  • InfluxDB 3 Core New
  • InfluxDB 3 Enterprise New
  • InfluxDB Clustered
  • InfluxDB 3 Cloud New
  • InfluxDB Cloud Serverless
  • InfluxDB Cloud Dedicated
  • InfluxDB 3 Explorer New

InfluxDB 2

  • InfluxDB OSS v2
  • InfluxDB Cloud (TSM)
  • Flux

InfluxDB 1

  • InfluxDB OSS v1
  • InfluxDB Enterprise
  • InfluxDB Cloud 1

Telegraf

  • Telegraf
  • Telegraf Controller New
  • Telegraf Enterprise New

Other products

  • Chronograf
  • Kapacitor
  • Kapacitor
  • Introduction
    • Install Kapacitor
    • Get started with Kapacitor
    • Docker Install
  • Work with Kapacitor
    • Using Kapacitor in Chronograf
    • Alerts overview
    • Alerts - Use Topics
    • Writing your own alert integration
    • Writing your own output node
    • Dynamic Data Scraping
    • Template tasks
    • Kapacitor API
    • Kapacitor CLI
    • Use Flux tasks
      • Manage Flux tasks
        • Create Flux tasks
        • List Flux tasks
        • Update Flux tasks
        • Manage Flux task runs
        • View Flux task logs
        • Retry failed Flux tasks
        • Delete Flux tasks
  • Guides
    • Calculate rates across series
    • Live leaderboard
    • Load directory service
    • Alerts based on two measurements
    • Custom anomaly detection
    • Reference TICKscripts
    • Hierarchical alert suppression
    • Kapacitor as a Continuous Query engine
    • Write socket-based UDFs
    • Set up event handler
    • Handle scheduled downtime
  • Administration
    • Upgrade to Kapacitor v1
    • Configure Kapacitor
    • Security
    • Authentication and authorization
      • Use Kapacitor authorizations
      • Use InfluxDB Enterprise authorizations
    • Manage subscriptions
  • Troubleshoot
    • Frequently asked questions (FAQs)
  • Reference
    • About the project
      • Contributing
      • CLA
      • License
      • Release notes
    • TICKscript language reference
      • Introduction
      • Syntax
      • Lambda expressions
      • Specification
    • TICKscript nodes
      • AlertNode
      • BarrierNode
      • BatchNode
      • ChangeDetectNode
      • CombineNode
      • DefaultNode
      • DeleteNode
      • DerivativeNode
      • EC2AutoscaleNode
      • EvalNode
      • FlattenNode
      • GroupByNode
      • HTTPOutNode
      • HTTPPostNode
      • InfluxDBOutNode
      • InfluxQLNode
      • JoinNode
      • K8sAutoscaleNode
      • KapacitorLoopback
      • LogNode
      • NoOpNode
      • QueryFluxNode
      • QueryNode
      • SampleNode
      • ShiftNode
      • SideloadNode
      • StateCountNode
      • StateDurationNode
      • StatsNode
      • StreamNode
      • SwarmAutoscaleNode
      • TrickleNode
      • UDFNode
      • UnionNode
      • WhereNode
      • WindowNode
      • FromNode
    • Event handlers
      • Aggregate
      • Alerta
      • BigPanda
      • Discord
      • Email
      • Exec
      • HipChat
      • Kafka
      • Log
      • Microsoft Teams
      • MQTT
      • OpsGenie
      • PagerDuty
      • Post
      • Publish
      • Pushover
      • Sensu
      • ServiceNow
      • Slack
      • SNMP Trap
      • TCP
      • Telegram
      • VictorOps
      • Zenoss
    • User types & permissions
    • Command line tools
      • kapacitor
        • kapacitor backup
        • kapacitor define
        • kapacitor define-template
        • kapacitor define-topic-handler
        • kapacitor delete
        • kapacitor disable
        • kapacitor enable
        • kapacitor flux
          • kapacitor flux task
            • kapacitor flux task create
            • kapacitor flux task delete
            • kapacitor flux task list
            • kapacitor flux task log
              • kapacitor flux task log list
            • kapacitor flux task retry-failed
            • kapacitor flux task run
              • kapacitor flux task run list
              • kapacitor flux task run retry
            • kapacitor flux task update
        • kapacitor help
        • kapacitor level
        • kapacitor list
        • kapacitor logs
        • kapacitor record
          • kapacitor record batch
          • kapacitor record query
          • kapacitor record stream
        • kapacitor reload
        • kapacitor replay
        • kapacitor replay-live
          • kapacitor replay-live batch
          • kapacitor replay-live query
        • kapacitor service-tests
        • kapacitor show
        • kapacitor show-template
        • kapacitor show-topic
        • kapacitor show-topic-handler
        • kapacitor stats
        • kapacitor vars
        • kapacitor version
        • kapacitor watch
      • kapacitord
        • kapacitord config
        • kapacitord downgrade
        • kapacitord help
        • kapacitord run
        • kapacitord version

    • Reference

  • Documentation MCP server

    • InfluxData Platform

  • Introduction
  • Get started
  • Documentation MCP server
  • Monitor
    • Monitor the InfluxData Platform
      • Configurations for monitoring
      • Monitoring dashboards
      • Configure a watcher of watchers
      • Other monitoring tools
        • InfluxDB _internal measurements
        • Kapacitor measurements
        • SHOW DIAGNOSTICS
        • SHOW STATS
    • Monitor containers
      • Monitor Kubernetes
  • Troubleshoot
    • Out-of-memory loops
    • Disk usage
  • Frequently asked questions
  • Identify version

CLA

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

  • InfluxDB Community Slack (Preferred)
  • InfluxData Community
  • InfluxDB Subreddit
Edit this page Submit docs issue Submit Kapacitor issue
© 2026 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

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.10 is now available

InfluxDB 3 Core 3.10 adds an automatic catalog format upgrade, a configurable query-concurrency limit, and processing engine improvements.

Key updates in InfluxDB 3 Core 3.10:

  • Catalog format upgrade: the on-disk catalog automatically upgrades from format v2 to v3 on first 3.10 startup. Migration is one-way—back up your catalog before upgrading.
  • --max-concurrent-queries: limit concurrent queries (adjustable at runtime).
  • GET /ready endpoint for readiness probes.
  • Processing engine: cross-database queries and trigger lockdown flags.

For more information, see the InfluxDB 3 Core release notes.

InfluxDB 3.10 is now available

InfluxDB 3 Enterprise 3.10 adds automated backup and restore, row-level deletions, and user management, with an automatic catalog format upgrade and performance preview improvements.

Key updates in InfluxDB 3 Enterprise 3.10:

  • Catalog format upgrade: the on-disk catalog automatically upgrades from format v2 to v3 on first 3.10 startup. Migration is one-way—back up your catalog before upgrading.
  • Automated backup and restore (beta)
  • Row-level deletions
  • User management (authentication and RBAC) — preview
  • Performance preview improvements

Backup and restore, row-level deletions, and the performance preview require the Enterprise storage engine upgrade (opt-in beta). Beta and preview features are subject to breaking changes and aren’t recommended for production use.

For more information, see the InfluxDB 3 Enterprise release notes

Telegraf Enterprise is now generally available

Telegraf Enterprise is now generally available, along with Telegraf Controller v1.0.

Telegraf Enterprise combines Telegraf Controller, a centralized management console for Telegraf, with official support from InfluxData. Manage configurations, monitor fleet health, and operate tens of thousands of Telegraf agents from a single system.

  • Read the announcement
  • Documentation
  • Download and install Telegraf Controller

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