Documentation

Overview of notebooks

Learn how notebooks can help to streamline and simplify your day-to-day business processes.

See an overview of notebook concepts, notebook controls, and notebook cell types also know as the basic building blocks of a notebook.

Notebook concepts

You can think of an InfluxDB notebook as a collection of sequential data processing steps. Each step is represented by a “cell” that performs an action such as querying, visualizing, processing, or writing data to your buckets. Notebooks help you do the following:

  • Create snippets of live code, equations, visualizations, and explanatory notes.
  • Create alerts or scheduled tasks.
  • Downsample and normalize data.
  • Build runbooks to share with your teams.
  • Output data to buckets.

Notebook controls

The following options appear at the top of each notebook.

Run

Select Run (or press Control+Enter) to display results of each cell and write data to the selected bucket.

Save Notebook (appears before first save)

Select Save Notebook to save all notebook cells. Once you’ve saved the notebook, this button disappears and the notebook automatically saves as subsequent changes are made.

Saving the notebook does not save cell results. When you open a saved notebook, click Run to update cell results.

Local or UTC timezone

Click the timezone drop-down list to select a timezone to use for the notebook. Select either the local time (default) or UTC.

Time range

Select from the options in the dropdown list or select Custom Time Range to enter a custom time range with precision up to nanoseconds, and then click Apply Time Range.

Share notebook

To generate a URL for the notebook, click the icon. For more detail, see how to share a notebook.

Notebook cell types

The following cell types are available for your notebook:

Data source

At least one data source (input) cell is required in a notebook for other cells to run.

  • Query Builder: Build a query with the Flux query builder.

  • Flux Script: Enter a raw Flux script.

    Data source cells work like the Query Builder or Script Editor in Data Explorer. For more information, see how to query data with Flux and the Data Explorer.

Visualization

  • Table: View your data in a table.
  • Graph: View your data in a graph.
  • Note: Create explanatory notes or other information for yourself or your team members.

Action


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

InfluxDB Cloud powered by TSM