Documentation

Load data from sources in the InfluxDB user interface (UI)

Load data from the following sources in the InfluxDB user interface (UI):

Load CSV or line protocol in UI

Load CSV or line protocol data by uploading a file or pasting the data manually into the UI.

  1. In the navigation menu on the left, click Load Data > Sources.

  2. Under File Upload, select the type of data to upload:

    • Annotated CSV. Verify your CSV file follows the supported annotated CSV syntax.

    • Line Protocol. Verify your line protocol file adheres to the following conventions:

      For more information, see supported line protocol syntax.

  3. Select the bucket to write to.

  4. Select the Precision in the dropdown menu. By default, the precision is set to nanoseconds.

  5. Do one of the following:

    • To upload file, drag and drop your file onto the UI, and then click Write Data.
    • To enter data manually, select the Enter Manually tab, paste your data, and then click Write Data.

Load data from a client library in the UI

  1. In the navigation menu on the left, click Load Data > Sources.

  2. Do one of the following:

    • Enter a specific client library to search for in the Search data writing methods field.
    • Scroll down to browse available client libraries.
  3. Click the client library to load data from.

  4. Under Code Sample Options, you’ll see a list of your InfluxDB tokens and buckets. Select both an API token and a bucket to write your data to. The selected API token and bucket are automatically added to scripts on the page that you can use to initialize a client and write data.

  5. Click the Copy to Clipboard buttons under a script to easily paste the script into your terminal or save the script to reuse for automation.

  6. Run the scripts on the page to do the following as needed:

    • Install the package, libraries, or client
    • Write data
    • Execute a Flux query

Load data from a Telegraf plugin in the UI

  1. In the navigation menu on the left, click Load Data > Sources.

  2. Do one of the following:

    • Enter a specific Telegraf plugin to search for in the Search data writing methods field.
    • Scroll down to Telegraf Plugins and browse available input plugins.
  3. Click the plugin to load data from. The plugin details page opens.

  4. Select one of the options from the Use this plugin dropdown:

    • Create a new configuration: Enter a configuration name and select an output bucket, and then click Continue Configuring.
    • Add to an existing configuration: Select an existing Telegraf configuration to add this plugin to, and then click Add to Existing Config.
  5. Provide a Telegraf Configuration Name and an optional Telegraf Configuration Description.

  6. Adjust configuration settings as needed. The configuration includes settings for the InfluxDB v2 output plugin to write to your bucket. To find configuration settings for a specific plugin, see Telegraf plugins.

  7. Click Save and Test. Your input plugin configuration is appended to the default agent settings and the InfluxDB output plugin configuration.

  8. The Test Your Configuration page provides instructions for how to start Telegraf using the generated configuration. See Start Telegraf below for detailed information about what each step does.

  9. Once Telegraf is running, click Listen for Data to confirm Telegraf is successfully sending data to InfluxDB. Once confirmed, a Connection Found! message appears.

  10. Click Finish. Your Telegraf configuration name and the associated bucket name appear in the list of Telegraf configurations.

  11. To view or edit the configuration, click the configuration name.

  12. To view default settings used to write data to InfluxDB, click InfluxDB Output Plugin.


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

InfluxDB Cloud powered by TSM