Documentation

InfluxQL SHOW statements

Use InfluxQL SHOW statements to query schema information from a database.

SHOW RETENTION POLICIES

Use the SHOW RETENTION POLICIES statement to list retention policies associated with a database. Each database has a single retention policy–autogen.

In InfluxDB 3 Core, retention policies are not part of the data structure but are expected by InfluxQL and used in fully-qualified measurements in the FROM clause. The data returned for each retention policy does not represent the actual retention-related attributes of the database. The values are placeholder values meant only for InfluxQL feature parity.

For information about database data retention, see List databases.

SHOW RETENTION POLICIES [ON <database-name>]

Examples

-- Show retention policies in the database specified in the query request
SHOW RETENTION POLICIES

-- Show retention policies in a specific database
SHOW RETENTION POLICIES ON "example-database"

SHOW MEASUREMENTS

Use the SHOW MEASUREMENTS statement to list measurements in a database.

SHOW MEASUREMENTS [with_measurement_clause] [where_clause] [limit_clause] [offset_clause]

Examples

-- Show all measurements
SHOW MEASUREMENTS

-- Show measurements where region tag = 'uswest' AND host tag = 'serverA'
SHOW MEASUREMENTS WHERE "region" = 'uswest' AND "host" = 'serverA'

-- Show measurements that start with 'h2o'
SHOW MEASUREMENTS WITH MEASUREMENT =~ /h2o.*/

SHOW FIELD KEYS

Use the SHOW FIELD KEYS statement to list all field keys in a measurement.

SHOW FIELD KEYS [from_clause]

Examples

-- Show field keys and field value data types from all measurements
SHOW FIELD KEYS

-- Show field keys and field value data types from specified measurement
SHOW FIELD KEYS FROM "cpu"

SHOW TAG KEYS

Use the SHOW TAG KEYS statement to list tag keys in a measurement.

SHOW TAG KEYS [from_clause] [where_clause] [limit_clause] [offset_clause]

Examples

-- Show all tag keys
SHOW TAG KEYS

-- Show all tag keys from the cpu measurement
SHOW TAG KEYS FROM "cpu"

-- Show all tag keys from the cpu measurement where the region key = 'uswest'
SHOW TAG KEYS FROM "cpu" WHERE "region" = 'uswest'

-- Show all tag keys where the host key = 'serverA'
SHOW TAG KEYS WHERE "host" = 'serverA'

SHOW TAG VALUES

Use the SHOW TAG VALUES statement to list values of specified tags in a database.

SHOW TAG VALUES [from_clause] WITH KEY = <tag-expression> [where_clause] [limit_clause] [offset_clause]

By default, the SHOW TAG VALUES statement only returns unique tag values from the last day. To modify the time range, include a WHERE clause with a time-based predicate.

Include a FROM clause

We strongly recommend including a FROM clause with the SHOW TAG VALUES statement that specifies 1-50 tables to query. Without a FROM clause, the InfluxDB query engine must read data from all tables and return unique tag values from each.

Depending on the number of tables in your database and the number of unique tag values in each table, excluding a FROM clause can result in poor query performance, query timeouts, or unnecessary resource allocation that may affect other queries.

Examples

-- Show tag values from the cpu measurement for the region tag
SHOW TAG VALUES FROM "cpu" WITH KEY = "region"

-- Show tag values from the cpu measurement for the region tag for a custom time range
SHOW TAG VALUES FROM "cpu" WITH KEY = "region" WHERE time > -7d

-- Show tag values from multiple measurements for the region tag
SHOW TAG VALUES FROM "cpu", "memory", "disk" WITH KEY = "region"

-- Show tag values from the cpu measurement for all tag keys that do not include the letter c
SHOW TAG VALUES FROM "cpu" WITH KEY !~ /.*c.*/

-- Show tag values from the cpu measurement for region & host tag keys where service = 'redis'
SHOW TAG VALUES FROM "cpu" WITH KEY IN ("region", "host") WHERE "service" = 'redis'

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