Documentation

logql.query_range() function

logql.query_range() is a user-contributed function maintained by the package author.

logql.query_range() queries data from a specified LogQL query within given time bounds, filters data by query, timerange, and optional limit expressions. All values are returned as string values (using raw mode in csv.from)

Function type signature
(
    query: string,
    ?end: A,
    ?limit: B,
    ?orgid: string,
    ?path: string,
    ?start: C,
    ?step: D,
    ?url: string,
) => stream[E] where A: Timeable, B: Stringable, C: Timeable, D: Stringable, E: Record

For more information, see Function type signatures.

Parameters

url

LogQL/qryn URL and port. Default is http://qryn:3100.

path

LogQL query_range API path.

limit

Query limit. Default is 100.

query

(Required) LogQL query to execute.

start

Earliest time to include in results. Default is -1h.

Results include points that match the specified start time. Use a relative duration or absolute time. For example, -1h or 2022-01-01T22:00:00.801064Z.

end

Latest time to include in results. Default is now().

Results exclude points that match the specified stop time. Use a relative duration or absolute time. For example, -1h or 2022-01-01T22:00:00.801064Z.

step

Query resolution step width in seconds. Default is 10.

Only applies to query types which produce a matrix response.

orgid

Optional Loki organization ID for partitioning. Default is "".

Examples

Query specific fields in a measurement from LogQL/qryn

import "contrib/qxip/logql"

option logql.defaultURL = "http://qryn:3100"

logql.query_range(query: "{job=\"dummy-server\"}", start: -1h, end: now(), limit: 100)

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: