Documentation

Use the influxdb3 CLI to query data

Use the influxdb3 query command to query data in InfluxDB 3 Core with SQL or InfluxQL.

Provide the following with your command:

  • Authorization token: Your InfluxDB 3 Core admin token

    with read permissions on the database. Provide this using one of the following:

    • --token command option
    • INFLUXDB3_AUTH_TOKEN environment variable
  • Database name: The name of the database to query. Provide this using one of the following:

    • -d, --database command option
    • INFLUXDB3_DATABASE_NAME environment variable
  • Query language (Optional): The query language of the query. Use the -l, --language option to specify one of the following query languages:

    • sql (default)
    • influxql
  • Query: SQL or InfluxQL query to execute. Provide the query in one of the following ways:

    • a string
    • the --file option and the path to a file that contains the query
    • from stdin
influxdb3 query \
  --token 
AUTH_TOKEN
\
--database
DATABASE_NAME
\
"SELECT * FROM home"
influxdb3 query \
  --token 
AUTH_TOKEN
\
--database
DATABASE_NAME
\
--file ./query.sql
cat ./query.sql | influxdb3 query --token 
AUTH_TOKEN
--database
DATABASE_NAME
influxdb3 query \
  --token 
AUTH_TOKEN
\
--language influxql \ --database
DATABASE_NAME
\
"SELECT * FROM home"
influxdb3 query \
  --token 
AUTH_TOKEN
\
--language influxql \ --file ./query.influxql
cat ./query.influxql | influxdb3 query \
  --token 
AUTH_TOKEN
\
--language influxql \ --database
DATABASE_NAME

In the examples above and below, replace the following:

  • DATABASE_NAME: Name of the database to query

Output format

The influxdb3 query command supports the following output formats:

Use the --format flag to specify the output format:

influxdb3 query \
  --token 
AUTH_TOKEN
\
--database
DATABASE_NAME
\
--format json \ "SELECT * FROM home WHERE time >= '2022-01-01T08:00:00Z' LIMIT 5"

View example pretty-formatted results

View example JSON-formatted results

View example JSON-line-formatted results

View example CSV-formatted results

Output query results to a Parquet file

To output query results to a Parquet file, provide the following options with the influxdb3 query command:

  • --format: parquet
  • -o, --output: the filepath to the Parquet file to store results in
influxdb3 query \
  --token 
AUTH_TOKEN
\
--database
DATABASE_NAME
\
--format parquet \ --output path/to/results.parquet \ "SELECT * FROM home WHERE time >= '2022-01-01T08:00:00Z' LIMIT 5"

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