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