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 Cloud Serverless, 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 bucket.

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!


The future of Flux

Flux is going into maintenance mode. You can continue using it as you currently are without any changes to your code.

Flux is going into maintenance mode and will not be supported in InfluxDB 3.0. This was a decision based on the broad demand for SQL and the continued growth and adoption of InfluxQL. We are continuing to support Flux for users in 1.x and 2.x so you can continue using it with no changes to your code. If you are interested in transitioning to InfluxDB 3.0 and want to future-proof your code, we suggest using InfluxQL.

For information about the future of Flux, see the following:

InfluxDB Cloud Serverless