Documentation

Work with regular expression types

A regular expression type represents a regular expression pattern.

Type name: regexp

Regular expression syntax

Flux uses the Go regexp implementation and syntax. This syntax is similar to regular expressions in Perl, Python, and other languages. Regular expression literals are enclosed in forward slash characters (/).

/^[a-z0-9]+$/

Use regular expression flags

Flux supports the following regular expression flags:

FlagDescription
icase-insensitive
mmulti-line mode: ^ and $ match begin/end line in addition to begin/end text
slet . match \n
Uungreedy: swap meaning of x* and x*?, x+ and x+?, etc

Include regular expression flags at the beginning of your regular expression pattern enclosed in parentheses (()) and preceded by a question mark (?).

/(?iU)foo*/

Use regular expressions in predicate expressions

To use regular expressions in predicate expressions, use the =~ and !~ comparison operators. The left operand must be a string. The right operand must be a regular expression.

"abc" =~ /\w/
// Returns true

"z09se89" =~ /^[a-z0-9]{7}$/
// Returns true

"foo" !~ /^f/
// Returns false

"FOO" =~ /(?i)foo/
// Returns true

Convert a string to a regular expression

  1. Import the regexp package.
  2. Use regexp.compile() to compile a string into a regular expression type.
import "regexp"

regexp.compile(v: "^- [a-z0-9]{7}")
// Returns ^- [a-z0-9]{7} (regexp type)

Examples

Replace all substrings that match a regular expression

  1. Import the regexp package.

  2. Use regexp.replaceAllString() and provide the following parameters:

    • r: regular expression
    • v: string to search
    • t: replacement for matches to r.
import "regexp"

regexp.replaceAllString(r: /a(x*)b/, v: "-ab-axxb-", t: "T")
// Returns "-T-T-"

Return the first regular expression match in a string

  1. Import the regexp package.

  2. Use regexp.findString() to return the first regular expression match in a string. Provide the following parameters:

    • r: regular expression
    • v: string to search
import "regexp"

regexp.findString(r: /foo.?/, v: "seafood fool")
// Returns "food"

Escape regular expression metacharacters in a string

If a string contains regular expression metacharacters that should be evaluated as literal characters, escape the metacharacters before converting the string to a regular expression:

  1. Import the regexp package.
  2. Use regexp.quoteMeta() and provide the string to escape regular expression metacharacters in:
import "regexp"

regexp.quoteMeta(v: ".+*?()|[]{}^$")
// Returns "\.\+\*\?\(\)\|\[\]\{\}\^\$"

Was this page helpful?

Thank you for your feedback!


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:

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