Documentation

influx delete

The influx delete command deletes points from an InfluxDB bucket in a specified time range. Select points to delete within the specified time range using delete predicate syntax.

Deleting data without a delete predicate

Running influx delete without the -p or --predicate flag deletes all data with timestamps between the specified --start and --stop times in the specified bucket.

Flags

Flag Description Input type Maps to ?
-c --active-config CLI configuration to use for command string
-b --bucket Name of bucket to remove data from (mutually exclusive with --bucket-id) string INFLUX_BUCKET_NAME
--bucket-id Bucket ID (mutually exclusive with --bucket) string INFLUX_BUCKET_ID
--configs-path Path to influx CLI configurations (default ~/.influxdbv2/configs) string INFLUX_CONFIGS_PATH
-h --help Help for the delete command
--host HTTP address of InfluxDB (default http://localhost:8086) string INFLUX_HOST
--http-debug Inspect communication with InfluxDB servers. string
-o --org Organization name (mutually exclusive with --org-id) string INFLUX_ORG
--org-id Organization ID (mutually exclusive with --org) string INFLUX_ORG_ID
-p --predicate InfluxQL-like predicate string (see Delete predicate) string
--skip-verify Skip TLS certificate verification INFLUX_SKIP_VERIFY
--start (Required) Start time in RFC3339 format (i.e. 2009-01-02T23:00:00Z) string
--stop (Required) Stop time in RFC3339 format (i.e. 2009-01-02T23:00:00Z) string
-t --token API token string INFLUX_TOKEN

Examples

Authentication credentials

The examples below assume your InfluxDB host, organization, and token are provided by either the active influx CLI configuration or by environment variables (INFLUX_HOST, INFLUX_ORG, and INFLUX_TOKEN). If you do not have a CLI configuration set up or the environment variables set, include these required credentials for each command with the following flags:

  • --host: InfluxDB host
  • -o, --org or --org-id: InfluxDB organization name or ID
  • -t, --token: InfluxDB API token
Delete all points in a measurement
influx delete \
  --bucket example-bucket \
  --start 1970-01-01T00:00:00Z \
  --stop $(date --utc +"%Y-%m-%dT%H:%M:%SZ") \
  --predicate '_measurement="example-measurement"'
Delete points in a measurement with a specific tag value
influx delete \
  --bucket example-bucket \
  --start 1970-01-01T00:00:00Z \
  --stop $(date --utc +"%Y-%m-%dT%H:%M:%SZ") \
  --predicate '_measurement="example-measurement" AND host="old-host"'
Delete all points within a specified time frame
influx delete \
  --bucket example-bucket \
  --start 2020-03-01T00:00:00Z \
  --stop 2020-11-14T00:00:00Z

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:

InfluxDB Cloud powered by TSM