Documentation

Retrieve system information for a query

Learn how to retrieve system information for a query in InfluxDB Cloud Dedicated.

In addition to the SQL standard information_schema, InfluxDB Cloud Dedicated contains system tables that provide access to InfluxDB-specific information. The information in each system table is scoped to the namespace you’re querying; you can only retrieve system information for that particular instance.

To get information about queries you’ve run on the current instance, use SQL to query the system.queries table, which contains information from the Querier instance currently handling queries.

The system.queries table is an InfluxDB 3 debug feature. To enable the feature and query system.queries, include an "iox-debug" header set to "true" and use SQL to query the table–for example:

from influxdb_client_3 import InfluxDBClient3
import secrets
import pandas

def get_query_information():
  print('# Get query information')

  client = InfluxDBClient3(token = f"
DATABASE_TOKEN
"
,
host = f"cluster-id.a.influxdb.io", database = f"
DATABASE_NAME
"
)
sql = "SELECT * FROM home WHERE time >= now() - INTERVAL '30 days'" try: client.query(sql) client.close() except Exception as e: print("Query error: ", e) client = InfluxDBClient3(token = f"
DATABASE_TOKEN
"
,
host = f"cluster-id.a.influxdb.io", database = f"
DATABASE_NAME
"
)
import time df = pandas.DataFrame() for i in range(0, 5): time.sleep(1) # Use SQL # To retrieve data about your query from the system.queries table, pass the following: # - the iox-debug: true request header # - an SQL query for system.queries reader = client.query(f'''SELECT compute_duration, query_type, query_text, success FROM system.queries WHERE issue_time >= now() - INTERVAL '1 day' ORDER BY issue_time DESC ''', headers=[(b"iox-debug", b"true")], mode="reader") df = reader.read_all().to_pandas() if df.shape[0]: break # Adjust pandas display options to avoid truncating the output # Filter the DataFrame to get rows where the column contains the query text filtered_df = df[df['query_text'] == sql] assert filtered_df.shape[0] > 0, "filtered_df should have at least 1 row" # Specify system.queries columns to output columns_to_output = ['compute_duration', 'query_text'] # Print row values for the specified columns print(filtered_df[columns_to_output]) get_query_information()

The output is similar to the following:

# Get query information
            compute_duration                                         query_text
3            0 days  SELECT * FROM home WHERE time >= now() - INTER...
4            0 days  SELECT * FROM home WHERE time >= now() - INTER...

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.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