Raw Query and Query Builder error

Products

• DX Operational Observability
• DX Operational Intelligence
• DX OI SaaS
• DX Application Performance Management

Issue/Introduction

A dashboard panel contains two or more queries, where at least one query uses the Raw Query editor with the "Metric Aggregations" option enabled, and another query is built with the Query Builder with "Metric Aggregations" disabled.

 

The panel does not render and displays the message "No data". The panel header shows the error indicator with the message:

 

Mandatory 'query' field missing

 

Inspecting the panel through Query Inspector shows that the HTTP call itself returns status 200, while one of the elements of the response contains: {"error": {"code": 500, "message": "Mandatory 'query' field missing", "traceId": "<trace id>"}}

 

The queries work correctly when they are placed in separate panels, or when they are all configured in the same mode.

Environment

DX Operational Observability SaaS and on-premise.
DX Operational Observability 25x, 26x on-premise.
Dashboards using the DX datasource plugin with the "Advance Query Builder" and "Metric Aggregations" options.

Cause

The request format is selected at panel level, not per query.

 

All queries of a panel are sent to the backend inside a single POST to /api/datasources/proxy/<datasource id>/query. As soon as one query of the panel has "Metric Aggregations" enabled, the whole panel is routed to the aggregation endpoint and every query of that panel is placed inside the same "NASAggregations" array.

 

The aggregation endpoint requires every element of that array to carry a "query" element containing the pipeline of operations (FROM, JOIN_TOPOLOGY, FILTER, JOIN_DATA, GROUP, SUM, ORDER, KEEP and so on).

 

A query built with the Query Builder while "Metric Aggregations" is disabled is serialized in the standard metric query format, which contains only "querySpecifier", "queryRange" and "clampSize", and has no "query" element. The backend therefore rejects that element with "Mandatory 'query' field missing".

 

A second confirmation that the two queries are built for two different API contracts is the time unit used in "queryRange" within the same request: the aggregation query uses milliseconds (for example endTime 1786139999000, rangeSize 691200000, frequency 3600000) while the non-aggregation query uses seconds (for example endTime 1786139999, rangeSize 691200, frequency 3600).

 

The panel displays "No data" even though the aggregation query returned results, because the failed query invalidates the data set consumed by the panel transformations.

 

In summary, a Raw Query or Query Builder query with "Metric Aggregations" enabled and a Query Builder query with "Metric Aggregations" disabled cannot be combined in the same panel.

Resolution

Use one of the two options below.

 

Option 1
Edit the panel, select the query that is failing, enable the "Metric Aggregations" option, and rewrite it as an aggregation query using the "query" pipeline. Keep the same "querySpecifier" already configured in the Query Builder (attributeNameSpecifier and sourceNameSpecifier), start the pipeline with the FROM operation and add the operations required for the expected result. Once every query of the panel is serialized in the aggregation format, the request is accepted and the panel renders.

 

Option 2

Split the queries into separate panels, one panel per mode. Note that any transformation that combines the two queries will no longer work, because transformations only operate on queries that belong to the same panel.

 

Additional Information

To confirm the condition, open the panel menu, select Inspect, then Query, and expand the request. In the "NASAggregations" array, the failing element is the one that does not contain the "query" key.

 

The HTTP call returns status 200 even when one of the queries fails. The failure is reported inside the corresponding element of the "nasResult" array, so the overall status code cannot be used to determine whether the panel executed successfully.