Documentation

Downsample data with notebooks

Create a notebook to downsample data. Downsampling aggregates or summarizes data within specified time intervals, reducing the overall disk usage as data collects over time.

The following example creates a notebook that queries Coinbase bitcoin price sample data from the last hour, downsamples the data into ten minute summaries, and then writes the downsampled data to an InfluxDB bucket.

  1. If you do not have an existing bucket to write the downsampled data to, create a new bucket.

  2. Create a new notebook.

  3. Select Past 1h from the time range drop-down list at the top of your notebook.

  4. In the Build a Query cell:

    1. In the FROM column under Sample, select Coinbase bitcoin price.
    2. In the next FILTER column, select _measurement from the drop-down list and select the coindesk measurement in the list of measurements.
    3. In the next FILTER column, select _field from the drop-down list, and select the price field from the list of fields.
    4. In the next FILTER column, select code from the drop-down list, and select a currency code.
  5. Click after your Build a Query cell to add a new cell and select Flux Script.

  6. In the Flux script cell:

    1. Use __PREVIOUS_RESULT__ to load the output of the previous notebook cell into the Flux script.

    2. Use aggregateWindow() to window data into ten minute intervals and return the average of each interval. Specify the following parameters:

      • every: Window interval (should be less than or equal to the duration of the queried time range). For this example, use 10m.
      • fn: Aggregate or selector function to apply to each window. For this example, use mean.
    3. Use to() to write the downsampled data back to an InfluxDB bucket.

    __PREVIOUS_RESULT__
        |> aggregateWindow(every: 10m, fn: mean)
        |> to(bucket: "example-bucket")
  7. (Optional) Click and select Note to add a note to describe your notebook, for example, “Downsample Coinbase bitcoin prices into hourly averages.”

  8. Click Run to run the notebook and write the downsampled data to your bucket.

Continuously run a notebook

To continuously run your notebook, export the notebook as a task:

  1. Click to add a new cell, and then select Task.

  2. Provide the following:

    • Every: Interval that the task should run at.
    • Offset: (Optional) Time to wait after the defined interval to execute the task. This allows the task to capture late-arriving data.
  3. Click Export as Task.


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

InfluxDB Cloud powered by TSM