Documentation

kapacitor delete

The kapacitor delete command deletes tasks, templates, recordings, replays, topics, or handlers.

Usage

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

Arguments

  • resource-type: Resource type to delete. The following resource types can be deleted:

    • tasks
    • templates
    • recordings
    • replays
    • topics
    • topic-handlers
  • topic: Topic to delete a handler from. Only required when deleting a handler.

  • resource-id-or-pattern: Resource ID or glob pattern to match resource IDs to delete.

Examples

Delete a task

kapacitor delete tasks my_task

Delete tasks matching a glob pattern

kapacitor delete tasks *_alert

Delete a recording

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

Delete a handler

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

kapacitor delete topic-handlers system slack

Was this page helpful?

Thank you for your feedback!


New in InfluxDB 3.7

Key enhancements in InfluxDB 3.7 and the InfluxDB 3 Explorer 1.5.

See the Blog Post

InfluxDB 3.7 is now available for both Core and Enterprise, landing alongside version 1.5 of the InfluxDB 3 Explorer UI. This release focuses on giving developers faster visibility into what their system is doing with one-click monitoring, a streamlined installation pathway, and broader updates that simplify day-to-day operations.

For more information, check out:

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On February 3, 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