Documentation

CEL functions and operators

CEL expressions for agent status evaluation support built-in CEL operators and the following function libraries.

Time functions

now()

Returns the current time. Use with last_update to calculate durations or detect stale data.

// True if more than 10 minutes since last heartbeat
now() - last_update > duration('10m')
// True if more than 5 minutes since last heartbeat
now() - last_update > duration('5m')

Math functions

Math functions from the CEL math library are available for numeric calculations.

Commonly used functions

FunctionDescriptionExample
math.greatest(a, b, ...)Returns the greatest value.math.greatest(log_errors, log_warnings)
math.least(a, b, ...)Returns the least value.math.least(agent.metrics_gathered, 1000)

Example

// Warn if either errors or warnings exceed a threshold
math.greatest(log_errors, log_warnings) > 5

String functions

String functions from the CEL strings library are available for string operations. These are useful when checking plugin alias or id fields.

Example

// Check if any input plugin has an alias containing "critical"
inputs.cpu.exists(i, has(i.alias) && i.alias.contains("critical"))

Encoding functions

Encoding functions from the CEL encoder library are available for encoding and decoding values.

Operators

CEL supports standard operators for building expressions.

Comparison operators

OperatorDescriptionExample
==Equalmetrics == 0
!=Not equallog_errors != 0
<Less thanagent.metrics_gathered < 100
<=Less than or equalbuffer_fullness <= 0.5
>Greater thanlog_errors > 10
>=Greater than or equalmetrics >= 1000

Logical operators

OperatorDescriptionExample
&&Logical ANDlog_errors > 0 && metrics == 0
||Logical ORlog_errors > 10 || log_warnings > 50
!Logical NOT!(metrics > 0)

Arithmetic operators

OperatorDescriptionExample
+Additionlog_errors + log_warnings
-Subtractionagent.metrics_gathered - agent.metrics_dropped
*Multiplicationlog_errors * 2
/Divisionagent.metrics_dropped / agent.metrics_gathered
%Modulometrics % 100

Ternary operator

// Conditional expression
log_errors > 10 ? true : false

List operations

FunctionDescriptionExample
exists(var, condition)True if any element matches.inputs.cpu.exists(i, i.errors > 0)
all(var, condition)True if all elements match.outputs.influxdb_v2.all(o, o.errors == 0)
size()Number of elements.inputs.cpu.size() > 0
has()True if a field or key exists.has(inputs.cpu)

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.9

Explorer 1.9 is now available with InfluxQL support, an AI-assisted Flux to SQL converter (beta), and new live sample data simulators.

View Explorer 1.9 release notes

Explorer 1.9 includes new features and improvements that make it easier to query, visualize, and manage data.

Highlights:

  • Flux to SQL converter (beta): Convert Flux queries to SQL with an AI-assisted converter.
  • InfluxQL support: Query data with InfluxQL in the Data Explorer and dashboards, and save and load InfluxQL queries.
  • InfluxQL visualizations: Render line and bar charts from InfluxQL results with per-tag series grouping.
  • Query error history: Review a history of query errors in the query tool.
  • Live sample data simulators: Generate continuous live sample data with new bird data and signal generator simulators.

For more details, see Explorer 1.9 release notes

InfluxDB 3.10 is now available

InfluxDB 3 Core 3.10 adds an automatic catalog format upgrade, a configurable query-concurrency limit, and processing engine improvements.

Key updates in InfluxDB 3 Core 3.10:

  • Catalog format upgrade: the on-disk catalog automatically upgrades from format v2 to v3 on first 3.10 startup. Migration is one-way—back up your catalog before upgrading.
  • --max-concurrent-queries: limit concurrent queries (adjustable at runtime).
  • GET /ready endpoint for readiness probes.
  • Processing engine: cross-database queries and trigger lockdown flags.

For more information, see the InfluxDB 3 Core release notes.

InfluxDB 3.10 is now available

InfluxDB 3 Enterprise 3.10 adds automated backup and restore, row-level deletions, and user management, with an automatic catalog format upgrade and performance preview improvements.

Key updates in InfluxDB 3 Enterprise 3.10:

  • Catalog format upgrade: the on-disk catalog automatically upgrades from format v2 to v3 on first 3.10 startup. Migration is one-way—back up your catalog before upgrading.
  • Automated backup and restore (beta)
  • Row-level deletions
  • User management (authentication and RBAC) — preview
  • Performance preview improvements

Backup and restore, row-level deletions, and the performance preview require the Enterprise storage engine upgrade (opt-in beta). Beta and preview features are subject to breaking changes and aren’t recommended for production use.

For more information, see the InfluxDB 3 Enterprise release notes

Telegraf Enterprise is now generally available

Telegraf Enterprise is now generally available, along with Telegraf Controller v1.0.

Telegraf Enterprise combines Telegraf Controller, a centralized management console for Telegraf, with official support from InfluxData. Manage configurations, monitor fleet health, and operate tens of thousands of Telegraf agents from a single system.

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On September 15, 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