VOOZH about

URL: https://docs.influxdata.com/influxdb/cloud/get-started/

⇱ Get started with InfluxDB Cloud | InfluxDB Cloud (TSM) Documentation


👁 Image
Documentation

InfluxDB Cloud (TSM)

Get started with InfluxDB Cloud

InfluxDB Cloud is the platform purpose-built to collect, store, process and visualize time series data. Time series data is a sequence of data points indexed in time order. Data points typically consist of successive measurements made from the same source and are used to track changes over time. Examples of time series data include:

  • Industrial sensor data
  • Server performance metrics
  • Heartbeats per minute
  • Electrical activity in the brain
  • Rainfall measurements
  • Stock prices

This multi-part tutorial walks you through writing time series data to InfluxDB Cloud, querying that data, processing and alerting on the data, and then visualizing the data.

Key concepts before you get started

Before you get started using InfluxDB, it’s important to understand how time series data is organized and stored in InfluxDB and some key definitions that are used throughout this documentation.

Data organization

The InfluxDB data model organizes time series data into buckets and measurements. A bucket can contain multiple measurements. Measurements contain multiple tags and fields.

  • Bucket: Named location where time series data is stored. A bucket can contain multiple measurements.
    • Measurement: Logical grouping for time series data. All points in a given measurement should have the same tags. A measurement contains multiple tags and fields.
      • Tags: Key-value pairs with values that differ, but do not change often. Tags are meant for storing metadata for each point–for example, something to identify the source of the data like host, location, station, etc.
      • Fields: Key-value pairs with values that change over time–for example: temperature, pressure, stock price, etc.
      • Timestamp: Timestamp associated with the data. When stored on disk and queried, all data is ordered by time.

For detailed information and examples of the InfluxDB data model, see Data elements.

Important definitions

The following are important definitions to understand when using InfluxDB:

  • Point: Single data record identified by its measurement, tag keys, tag values, field key, and timestamp.

  • Series: A group of points with the same

    measurement, tag keys and values, and field key.

Example InfluxDB query results
_time_measurementcitycountry_field_value
2022-01-01T12:00:00ZweatherLondonUKtemperature12.0
2022-02-01T12:00:00ZweatherLondonUKtemperature12.1
2022-03-01T12:00:00ZweatherLondonUKtemperature11.5
2022-04-01T12:00:00ZweatherLondonUKtemperature5.9
_time_measurementcitycountry_field_value
2022-01-01T12:00:00ZweatherCologneDEtemperature13.2
2022-02-01T12:00:00ZweatherCologneDEtemperature11.5
2022-03-01T12:00:00ZweatherCologneDEtemperature10.2
2022-04-01T12:00:00ZweatherCologneDEtemperature7.9
_time_measurementcitycountry_field_value
2022-01-01T12:00:00ZweatherLondonUKhumidity88.4
2022-02-01T12:00:00ZweatherLondonUKhumidity94.0
2022-03-01T12:00:00ZweatherLondonUKhumidity82.1
2022-04-01T12:00:00ZweatherLondonUKhumidity87.6
_time_measurementcitycountry_field_value
2022-01-01T12:00:00ZweatherCologneDEhumidity88.5
2022-02-01T12:00:00ZweatherCologneDEhumidity87.8
2022-03-01T12:00:00ZweatherCologneDEhumidity76.4
2022-04-01T12:00:00ZweatherCologneDEhumidity93.3

Tools to use

Throughout this tutorial, there are multiple tools you can use to interact with InfluxDB Cloud. Examples are provided for each of the following:

InfluxDB user interface (UI)

The InfluxDB UI provides a web-based visual interface for interacting with and managing InfluxDB.

To access the InfluxDB Cloud UI, log into your InfluxDB Cloud account.

influx CLI

The influx CLI lets you interact with and manage InfluxDB Cloud from a command line.

For detailed CLI installation instructions, see Use the influx CLI.

InfluxDB HTTP API

The InfluxDB API provides a simple way to interact with the InfluxDB Cloud using HTTP(S) clients. Examples in this tutorial use cURL, but any HTTP(S) client will work.

InfluxDB client libraries

InfluxDB client libraries are language-specific clients that interact with the InfluxDB HTTP API. Examples for client libraries are not provided in this tutorial, but these can be used to perform all the actions outlined in this tutorial.

Authorization

InfluxDB Cloud requires authentication using API tokens. Each API token is associated with a user and a specific set of permissions for InfluxDB resources.


👁 InfluxDB University

InfluxDB Essentials

Learn how to write, query, and visualize data in InfluxDB in this free InfluxDB University course.


Was this page helpful?

Thank you for your feedback!


Support and feedback

Thank you for being part of our community! We welcome and encourage your feedback and bug reports for InfluxDB Cloud (TSM) and this documentation. To find support, use the following resources:

Customers with an annual or support contract can contact InfluxData Support.

© 2026 InfluxData, Inc.

Select your InfluxDB Cloud region

Select your InfluxDB Cloud region and cluster and we’ll customize code examples for you. Identify your InfluxDB Cloud cluster.

AWS
  • US West (Oregon)

GCP
Azure

For more information, see InfluxDB Cloud regions.

Thank you for your feedback!

Let us know what we can do better:

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

You are currently viewing documentation specific to InfluxDB Cloud powered by the TSM storage engine, which offers different functionality than InfluxDB Cloud Serverless powered by the v3 storage engine.

Are you using InfluxDB Cloud powered by TSM? How to find out?

Visit your organization's homepage and find the following at the bottom of the right column:

InfluxDB Cloud powered by TSM Storage Engine Version 2