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!


Introducing InfluxDB Clustered

A highly available InfluxDB 3.0 cluster on your own infrastructure.

InfluxDB Clustered is a highly available InfluxDB 3.0 cluster built for high write and query workloads on your own infrastructure.

InfluxDB Clustered is currently in limited availability and is only available to a limited group of InfluxData customers. If interested in being part of the limited access group, please contact the InfluxData Sales team.

Learn more
Contact InfluxData Sales

The future of Flux

Flux is going into maintenance mode. You can continue using it as you currently are without any changes to your code.

Flux is going into maintenance mode and will not be supported in InfluxDB 3.0. This was a decision based on the broad demand for SQL and the continued growth and adoption of InfluxQL. We are continuing to support Flux for users in 1.x and 2.x so you can continue using it with no changes to your code. If you are interested in transitioning to InfluxDB 3.0 and want to future-proof your code, we suggest using InfluxQL.

For information about the future of Flux, see the following: