Free tools Windows power users keep installed
One-click scans. No signup required.
To query InfluxDB, first check which version you use: InfluxDB 3 Core supports SQL and InfluxQL, but not Flux; InfluxDB v2 documentation covers Flux and InfluxQL, while v1’s query-language documentation centers on InfluxQL. Then choose the matching syntax, set a time range, and run the query through an interface supported by that version.
Check your InfluxDB version before writing a query
InfluxDB query languages and execution options differ by generation. The InfluxDB 3 Core query documentation supports SQL and InfluxQL. Flux is not supported in InfluxDB 3 Core. The InfluxDB v2 getting-started guide covers Flux and InfluxQL, and the InfluxDB v1 query-language documentation centers on InfluxQL.
Identify the version and edition of the server or service you are connecting to before copying an example. Syntax, data naming, and available query interfaces are not interchangeable across all InfluxDB versions.
Choose the query language that fits your version and task
| Version or context | Available language in the cited documentation | What to know |
|---|---|---|
| InfluxDB 3 Core | SQL and InfluxQL | Core SQL is based on Apache DataFusion and includes joins, unions, and window functions. InfluxQL is more limited and can suit existing v1-style queries and APIs. Flux is unsupported. InfluxData documentation |
| InfluxDB v2 | Flux and InfluxQL | Flux uses a functional pipeline; InfluxQL uses SQL-like statements and, in the documented v2/Cloud TSM context, needs a bucket-to-DBRP mapping. InfluxData documentation and DBRP documentation |
| InfluxDB v1 | InfluxQL | The cited v1 query-language documentation describes InfluxQL. InfluxData documentation |
For InfluxDB 3 Core, choose SQL for broader relational operations such as joins or window functions, or InfluxQL when maintaining compatible time-series query syntax is the priority. For v2, use Flux or InfluxQL only in a configuration that supports it; do not assume an InfluxDB 3 Core server accepts Flux.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchQuery with Flux in InfluxDB v2
A Flux query selects a bucket with from(), limits the data to a time interval with range(), and then applies filters. The range is required: InfluxDB’s Flux documentation says that from() must be followed by range() because queries must be time-bound. See Query InfluxDB with Flux.
from(bucket: "example-bucket")
|> range(start: -1h)
|> filter(fn: (r) => r._measurement == "home")This example reads the last hour from the home measurement in example-bucket. Add further filter() steps to narrow by field, tag, or value as appropriate for the data. Flux documentation for remote queries also uses a host, organization, and token; treat tokens as credentials and do not place a real token in code you share or publish.
Query with InfluxQL
InfluxQL uses a SQL-like structure: SELECT identifies fields or calculations, FROM identifies a measurement, and an optional WHERE clause filters records, including by time. This v2-guide pattern uses a time-bounded query:
SELECT temp, room
FROM home
WHERE time >= '2022-01-01T08:00:00Z'
AND time <= '2022-01-01T20:00:00Z'In InfluxDB v2 or Cloud TSM, InfluxQL addresses a bucket through a database and retention policy (DBRP) mapping. Set up that mapping before querying the bucket with InfluxQL; without it, the legacy database-and-retention-policy naming model does not identify the bucket for this query path. See InfluxQL in InfluxDB v2.
The v2 getting-started guide notes that its UI does not provide a way to query with InfluxQL and points to Chronograf or Grafana for that use. This is a v2-specific interface note, not a general restriction across all InfluxDB releases.
Query InfluxDB 3 Core with SQL
In InfluxDB 3 Core, SQL can select from a table and constrain results by time. The Core documentation describes a query range of approximately 72 hours, recent or historical, to support performance. Use a range within that documented limit and check the current behavior for your Core edition.
Rank #4
SELECT *
FROM home
WHERE time >= now() - INTERVAL '2 days'
ORDER BY timeThis example requests the last two days from the home table. The interval is kept within the approximate limit described for Core; the actual limit should not be generalized to InfluxDB v1, v2, or other editions. Core documents the influxdb3 query command, where you specify a database and choose SQL or InfluxQL; see the Core query reference for current command syntax.
Where to run an InfluxDB query
For v2, the getting-started documentation lists the UI, HTTP API, influx CLI, Chronograf, Grafana, and client libraries as query routes. The appropriate route depends on both the language and the interface’s support for it: for example, the cited v2 UI does not offer InfluxQL querying, while Chronograf or Grafana can be used for that v2 case.
For InfluxDB 3 Core, use its documented influxdb3 query command and provide the target database and language. Refer to the documentation for your exact edition and version rather than assuming a v2 UI or CLI path applies to Core.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
