Documentation

Regular expressions

InfluxQL supports using regular expressions when specifying:

Regular expressions in InfluxQL only support string comparisons and can only evaluate fields with string values.

Note: Regular expression comparisons are more computationally intensive than exact string comparisons. Queries with regular expressions are not as performant as those without.

Syntax

SELECT /<regular_expression_field_key>/ FROM /<regular_expression_measurement>/ WHERE [<tag_key> <operator> /<regular_expression_tag_value>/ | <field_key> <operator> /<regular_expression_field_value>/] GROUP BY /<regular_expression_tag_key>/

Regular expressions are surrounded by / characters and use Golang’s regular expression syntax.

Supported operators

=~: matches against !~: doesn’t match against

Examples

Use a regular expression to specify field keys and tag keys in the SELECT clause

Use a regular expression to specify measurements in the FROM clause

Use a regular expression to specify tag values in the WHERE clause

Use a regular expression to specify a tag with no value in the WHERE clause

Use a regular expression to specify a tag with a value in the WHERE clause

Use a regular expression to specify a field value in the WHERE clause

Use a regular expression to specify tag keys in the GROUP BY clause


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: