Documentation

Query SQLite

To query SQLite with Flux:

  1. Import the sql package.

  2. Use sql.from() and provide the following parameters:

    • driverName: sqlite3
    • dataSourceName: See data source name
    • query: SQL query to execute
import "sql"

sql.from(
    driverName: "sqlite3",
    dataSourceName: "file:/path/to/example.db?cache=shared&mode=ro",
    query: "SELECT * FROM example_table",
)

Requires file system access

To query SQLite, Flux must have access to the filesystem. If Flux does not have access to the file system, the query will return an error similar to one of the following:

  • Error: unable to open database file
  • failed to read file: filesystem service is uninitialized
  • An internal error has occurred

If using InfluxDB Cloud or InfluxDB OSS, the Flux process does not have access to the filesystem.


SQLite data source name

The sqlite3 driver uses the following DSN syntax (also known as a connection string):

file:/path/to/example.db?param=value

SQLite to Flux data type conversion

sql.from() converts SQLite data types to Flux data types.

SQLite data typeFlux data type
INT, INTEGER, BIGINT, SMALLINT, TINYINTint
FLOAT, DOUBLEfloat
DATETIME, TIMESTAMP, DATEtime
BOOLint
TEXTstring

All other SQLite data types are converted to strings.


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:

Telegraf Controller v0.0.6-beta now available

Telegraf Controller v0.0.6-beta is now available with new features, improvements, and bug fixes.

View the release notes
Download Telegraf Controller v0.0.6-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