Documentation

Work with Kapacitor

The documents in this section present the key features of the Kapacitor daemon (kapacitord) and the Kapacitor client (kapacitor).

  • Kapacitor and Chronograf – presents how Kapacitor is integrated with the Chronograf graphical user interface application for managing tasks and alerts.
  • Kapacitor API Reference documentation – presents the HTTP API and how to use it to update tasks and the Kapacitor configuration.
  • Alerts - Overview – presents an overview of the Kapacitor alerting system.
  • Alerts - Using topics – a walk-through on creating and using alert topics.
  • Alerts - Event handler setup – presents setting up event handlers for HipChat and Telegraf, which can serve as a blueprint for other event handlers.
  • Dynamic data scraping – introduces the discovery and scraping features, which allow metrics to be dynamically pulled into Kapacitor and then written to InfluxDB.

Was this page helpful?

Thank you for your feedback!


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