Documentation

Delete predicate syntax

InfluxDB uses an InfluxQL-like predicate syntax to determine what data points to delete. InfluxDB uses the delete predicate to evaluate the series keys of points in the time range specified in the delete request. Points with series keys that evaluate to true for the given predicate are deleted. Points with series keys that evaluate to false are preserved.

A delete predicate is comprised of one or more predicate expressions. The left operand of the predicate expression is the column name. The right operand is the column value. Operands are compared using comparison operators. Use logical operators to combine two or more predicate expressions.

Example delete predicate
key1="value1" AND key2="value"

Predicates with special characters or keywords

If your predicate contains keywords or strings with special characters, wrap each in escaped quotes to ensure the predicate string is parsed correctly.

Because delete predicates follow InfluxQL syntax, any InfluxQL keyword that matches your tag name needs to be escaped. Keywords are case-insensitive.

// Escaped due to the "-"
"_measurement=\"example-dash\""

// Escaped because "Name" is a keyword
"_measurement=example and \"Name\"=predicate"

Column limitations when deleting data

InfluxDB Cloud supports deleting data by any column or tag except the following:

  • _time

  • _value

Logical operators

Logical operators join two or more predicate expressions.

OperatorDescription
ANDBoth left and right operands must be true for the expression to be true.

Comparison operators

Comparison operators compare left and right operands and return true or false.

OperatorDescriptionExampleResult
=Equal to"abc"="abc"true

Delete predicate examples

Delete points by measurement

The following will delete points in the sensorData measurement:

_measurement="sensorData"

Delete points by field

The following will delete points with the temperature field:

_field="temperature"

Delete points by tag set

The following will delete points from the prod-1.4 host in the us-west region:

host="prod-1.4" AND region="us-west"

Limitations

The delete predicate syntax has the following limitations.

  • Delete predicates do not support regular expressions.
  • Delete predicates do not support the OR logical operator.
  • Delete predicates only support equality (=), not inequality (!=).
  • Delete predicates can use any column or tag except _time

or _value.


Was this page helpful?

Thank you for your feedback!


InfluxDB OSS 2.9.0: API tokens are hashed by default

Stronger token security in InfluxDB OSS 2.9.0 — tokens are hashed on disk by default. Existing tokens are hashed on first startup and can’t be recovered afterward. Capture any plaintext tokens you still need before you upgrade.

View InfluxDB OSS 2.9.0 release notes

Hashed tokens authenticate exactly like unhashed tokens — clients and integrations keep working.

Also new in 2.9.0:

  • Configurable backup compression
  • Restore support for backups containing hashed tokens
  • Tighter Edge Data Replication queue validation
  • Flux upgrade
  • Compaction reliability improvements

Key enhancements in Explorer 1.8

Explorer 1.8 is now available with streaming data subscriptions (beta), line protocol preview, and query history & saved queries.

View Explorer 1.8 release notes

Explorer 1.8 includes new features and improvements that make it easier to ingest, explore, and manage data.

Highlights:

  • Streaming data subscriptions (beta): Stream data into Explorer from MQTT, Kafka, and AMQP sources.
  • Line protocol preview: Preview line protocol, schema, and parse errors before data is written.
  • Custom sample data: Generate custom sample datasets with line protocol and schema preview.
  • Query history and saved queries: Browse query history and save/re-run named queries.
  • Retention period management: Set, update, or clear retention periods on databases and tables.

For more details, see Explorer 1.8 release notes

InfluxDB 3.9: Performance upgrade preview

InfluxDB 3 Enterprise 3.9 includes a beta of major performance upgrades with faster single-series queries, wide-and-sparse table support, and more.

InfluxDB 3 Enterprise 3.9 includes a beta of major performance and feature updates.

Key improvements:

  • Faster single-series queries
  • Consistent resource usage
  • Wide-and-sparse table support
  • Automatic distinct value caches for reduced latency with metadata queries

Preview features are subject to breaking changes.

For more information, see:

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:

Telegraf Controller v0.0.7-beta now available

Telegraf Controller v0.0.7-beta is now available with new features, improvements, bug fixes, and an important breaking change.

View the release notes
Download Telegraf Controller v0.0.7-beta

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

InfluxDB Cloud powered by TSM