Documentation

influxdb3 query

The influxdb3 query command executes a query against a running InfluxDB 3 Enterprise server.

Usage

influxdb3 query [OPTIONS] --database <DATABASE_NAME> [QUERY]...
Aliases

query, q

Arguments

  • QUERY: The query to execute. Provide the query in one of the following ways:

    • a string
    • a path to a file that contains the query using the --file option
    • from stdin

Options

OptionDescription
-H--hostHost URL of the running InfluxDB 3 Enterprise server (default is http://127.0.0.1:8181)
-d--database(Required) Name of the database to operate on
--token(Required) Authentication token
-l--languageQuery language of the query string (sql (default) or influxql)
--formatOutput format (pretty (default), json, jsonl, csv, parquet)
-o--outputOutput query results to the specified file
-f--fileA file that contains the query to execute
--tls-caPath to a custom TLS certificate authority (for testing or self-signed certificates)
-h--helpPrint help information
--help-allPrint detailed help information

Option environment variables

You can use the following environment variables to set command options:

Environment VariableOption
INFLUXDB3_HOST_URL--host
INFLUXDB3_DATABASE_NAME--database
INFLUXDB3_AUTH_TOKEN--token

Examples

In the examples below, replace DATABASE_NAME: with the name of the database to query.

Query data using SQL

influxdb3 query \
  --database 
DATABASE_NAME
\
--token AUTH_TOKEN \ 'SELECT * FROM home'
influxdb3 query \
  --database 
DATABASE_NAME
\
--token AUTH_TOKEN \ --file ./query.sql
cat ./query.sql | influxdb3 query \
  --database 
DATABASE_NAME
\
--token AUTH_TOKEN \

Query data using InfluxQL

influxdb3 query \
  --language influxql \
  --database 
DATABASE_NAME
\
--token AUTH_TOKEN \ 'SELECT * FROM home'
influxdb3 query \
  --language influxql \
  --database 
DATABASE_NAME
\
--token AUTH_TOKEN \ --file ./query.influxql
cat ./query.influxql | influxdb3 query \
  --language influxql \
  --database 
DATABASE_NAME
\
--token AUTH_TOKEN

Query data and return JSON-formatted results

influxdb3 query \
  --format json \
  --database 
DATABASE_NAME
\
--token AUTH_TOKEN \ 'SELECT * FROM home'
influxdb3 query \
  --format json \
  --database 
DATABASE_NAME
\
--token AUTH_TOKEN \ --file ./query.sql
cat ./query.sql | influxdb3 query \
  --format json \
  --database 
DATABASE_NAME
\
--token AUTH_TOKEN \

Query data and write results to a file

influxdb3 query \
  --output /path/to/results.txt \
  --database 
DATABASE_NAME
\
--token AUTH_TOKEN \ 'SELECT * FROM home'
influxdb3 query \
  --output /path/to/results.txt \
  --database 
DATABASE_NAME
\
--token AUTH_TOKEN \ --file ./query.sql
cat ./query.sql | influxdb3 query \
  --output /path/to/results.txt \
  --database 
DATABASE_NAME
\
--token AUTH_TOKEN

Was this page helpful?

Thank you for your feedback!


New in InfluxDB 3.5

Key enhancements in InfluxDB 3.5 and the InfluxDB 3 Explorer 1.3.

See the Blog Post

InfluxDB 3.5 is now available for both Core and Enterprise, introducing custom plugin repository support, enhanced operational visibility with queryable CLI parameters and manual node management, stronger security controls, and general performance improvements.

InfluxDB 3 Explorer 1.3 brings powerful new capabilities including Dashboards (beta) for saving and organizing your favorite queries, and cache querying for instant access to Last Value and Distinct Value caches—making Explorer a more comprehensive workspace for time series monitoring and analysis.

For more information, check out:

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On February 3, 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