Query editor

The Infinity query editor allows you to retrieve data from HTTP endpoints and transform it for visualization in Grafana. This document explains the query editor interface and how to build queries.

Before you begin

You must have a configured Infinity data source. Refer to Configure the Infinity data source for instructions.
Familiarize yourself with the data format you want to query (JSON, CSV, XML, GraphQL, or HTML).

Query editor overview

The query editor consists of several key components:

Component	Description
Type	The data format to query: JSON, CSV, TSV, XML, GraphQL, or HTML
Parser	How to process the data: Default, JSONata, JQ, UQL, or GROQ
Source	Where to get the data: URL, Inline, Azure Blob, or Reference
Format	Output format: Table, Time series, Data frame, Logs, Trace, or Node graph

Create a query

To create a basic query:

In the query editor, select the Type that matches your data format (for example, JSON).
Select a Parser based on your transformation needs:
- JSONata (default) - JSONata expressions, runs in backend (supports alerting)
- JQ - JQ expressions, runs in backend (supports alerting)
- UQL - Unstructured Query Language, runs in frontend
- Frontend - Simple column mapping, runs in frontend
Select the Source:
- URL - Fetch data from an HTTP endpoint
- Inline - Enter data directly in the editor
- Azure Blob - Retrieve from Azure Blob Storage
- Reference - Use pre-configured reference data
Select the output Format based on your visualization needs.
If using URL source, enter the endpoint URL and configure the HTTP method.

URL configuration

When using URL as the source:

Setting	Description
Method	HTTP method: GET or POST. PUT, PATCH, and DELETE are available only when Allow dangerous HTTP methods is enabled in the data source configuration.
URL	The endpoint URL
Headers, Request params	Click to configure additional headers and query parameters

Use variables in URLs

You can use Grafana variables and time macros in URLs:

https://api.example.com/data?from=${__timeFrom}&to=${__timeTo}

For more information about URL configuration, refer to URL configuration.

Parsing options

The Parsing options & Result fields section configures how data is extracted:

Setting	Description
Rows/Root	JSONata or JQ selector that returns an array of elements from the API response
Columns	Define which fields to extract and their data types

Configure columns

Click Add Columns to define the fields to extract:

Property	Description
Selector	Path to the field in your data
Title	Display name for the column
Type	Data type: String, Number, Time, Time (UNIX ms), Time (UNIX s), or Boolean

Computed columns, filters, and grouping

The Computed columns, Filter, Group by section provides additional data transformation options when using backend parsers (JSONata or JQ):

Feature	Description
Computed Columns	Create new fields using expressions (for example, `price * qty`)
Filter	Filter rows using expressions (for example, `age >= 18`)
Summarize	Aggregate data using functions like `sum()`, `count()`, `mean()`
Summarize By	Group aggregations by a field
Summarize Alias	Name for the summarized result

For detailed information about expressions and operators, refer to JSONata backend parser.

Parser options

Choose a parser based on your needs:

Parser	Runs in	Alerting support	Best for
JSONata (default)	Backend	Yes	Complex transformations, alerting
JQ	Backend	Yes	JQ-style queries, alerting
UQL	Frontend	No	SQL-like queries, pivoting
Frontend	Frontend	No	Simple queries with column mapping

For detailed parser documentation:

Output formats

Select the appropriate format for your visualization:

Format	Use case
Table	Display data in table panels
Time series	Time-based data for graph panels
Data frame	Generic format for most visualizations
Logs	Log data for the Logs panel
Trace	Trace data for the Traces panel
Node graph (nodes/edges)	Network topology visualization

For specialized formats, refer to:

Use queries for alerting

To use Infinity queries with Grafana Alerting, you must use a backend parser (JSONata or JQ). Frontend parsers (Default, UQL, GROQ) do not support alerting.

Backend parsers also enable: