Documentation

kapacitor list

The kapacitor list command lists tasks, templates, recordings, replays, topics, or handlers and their current state.

Usage

kapacitor list <resource-type> [<topic>] [<resource-id-or-pattern>]

Arguments

  • resource-type: Resource type to list. The following resource are supported:

    • tasks
    • templates
    • recordings
    • replays
    • topics
    • topic-handlers
    • service-tests
  • topic: Topic to list handlers from. Only required when listing handlers.

  • resource-id-or-pattern: Resource ID or glob pattern to match resource IDs to list. If no resource ID or pattern is specified, all resources of the specified resource type are listed.

Examples

List all tasks

kapacitor list tasks

List all tasks matching a glob pattern

kapacitor list tasks *_alert

List a specific recording

kapacitor list recordings b0a2ba8a-aeeb-45ec-bef9-1a2939963586

List all handlers in a topic

kapacitor list topic-handlers system

List a specific handler in a topic

To list a handler, specify the topic before the handler ID or glob pattern.

kapacitor list topic-handlers system email

Was this page helpful?

Thank you for your feedback!


Telegraf Enterprise now in public beta

Get early access to the Telegraf Controller and provide feedback to help shape the future of Telegraf Enterprise.

See the Blog Post

The upcoming Telegraf Enterprise offering is for organizations running Telegraf at scale and is comprised of two key components:

  • Telegraf Controller: A control plane (UI + API) that centralizes Telegraf configuration management and agent health visibility.
  • Telegraf Enterprise Support: Official support for Telegraf Controller and Telegraf plugins.

Join the Telegraf Enterprise beta to get early access to the Telegraf Controller and provide feedback to help shape the future of Telegraf Enterprise.

For more information:

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On May 27, 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