InfluxDB system tables

InfluxDB system measurements contain time series data used by and generated from the InfluxDB internal monitoring system.

Each InfluxDB Cloud Dedicated namespace includes the following system measurements:

system.queries measurement

The system.queries measurement stores log entries for queries executed for the provided namespace (database) on the node that is currently handling queries.

from influxdb_client_3 import InfluxDBClient3
client = InfluxDBClient3(token = DATABASE_TOKEN,
                          host = HOSTNAME,
                          org = '',
client.query('select * from home')
reader = client.query('''
                      SELECT *
                      FROM system.queries
                      WHERE issue_time >= now() - INTERVAL '1 day'
                      AND query_text LIKE '%select * from home%'
                    headers=[(b"iox-debug", b"true")],
print("# system.queries schema\n")

system.queries has the following schema:

# system.queries schema

issue_time: timestamp[ns] not null
query_type: string not null
query_text: string not null
completed_duration: duration[ns]
success: bool not null
trace_id: string

When listing measurements (tables) available within a namespace, some clients and query tools may include the queries table in the list of namespace tables.

system.queries reflects a process-local, in-memory, namespace-scoped query log. The query log isn’t shared across instances within the same deployment. While this table may be useful for debugging and monitoring queries, keep the following in mind:

  • Records stored in system.queries are volatile.
    • Records are lost on pod restarts.
    • Queries for one namespace can evict records from another namespace.
  • Data reflects the state of a specific pod answering queries for the namespace—-the log view is scoped to the requesting namespace and queries aren’t leaked across namespaces.
    • A query for records in system.queries can return different results depending on the pod the request was routed to.

Data retention: System data can be transient and is deleted on pod restarts. The log size per instance is limited and the log view is scoped to the requesting namespace.

system.queries schema

  • system.queries (measurement)
    • fields:
      • issue_time: timestamp when the query was issued
      • query_type: type (syntax: sql, flightsql, or influxql) of the query
      • query_text: query statement text
      • success: execution status (boolean) of the query
      • completed_duration: time (duration) that the query took to complete
      • trace_id: trace ID for debugging and monitoring events

Was this page helpful?

Thank you for your feedback!

Introducing InfluxDB Clustered

A highly available InfluxDB 3.0 cluster on your own infrastructure.

InfluxDB Clustered is a highly available InfluxDB 3.0 cluster built for high write and query workloads on your own infrastructure.

InfluxDB Clustered is currently in limited availability and is only available to a limited group of InfluxData customers. If interested in being part of the limited access group, please contact the InfluxData Sales team.

Learn more
Contact InfluxData Sales

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:

State of the InfluxDB Cloud Serverless documentation

InfluxDB Cloud Serverless documentation is a work in progress.

The new documentation for InfluxDB Cloud Serverless is a work in progress. We are adding new information and content almost daily. Thank you for your patience!

If there is specific information you’re looking for, please submit a documentation issue.