Query inspection
The Queries page in Cube Cloud is a one-stop shop for all performance and diagnostic information about queries issued for a deployment. It is kept up-to-date in real time and provides a quick way to check whether queries are being accelerated with pre-aggregations, how long they took to execute, and if they failed.
By default, Cube Cloud shows you a live feed of queries made to the API and connected data sources. You can see query history for the last 72 hours by using the date picker in the top right corner of the page and selecting a time period:
To go back to live mode, click :
You can switch between queries made to the API and queries made to connected data sources by switching between the and tabs.
Clicking will show all queries in order of recency, while will show the most-frequently executed queries:
You can also use filters to find problematic queries; you can filter by query duration, cache status, whether the query was accelerated, and by failing queries:
To see an expanded view of a query, click on next to any query:
This will show us how long the query took, whether the query was accelerated, and even view the raw query by clicking :
To drill down on a specific query, click it to see more information.
The tab shows the raw JSON query sent to the Cube Cloud deployment.
If the query failed, the tab will show you the error message and stacktrace:
The tab shows the generated SQL query sent by Cube to either your data source or Cube Store if the query was accelerated with a pre-aggregation:
The tab shows the pre-aggregation used to accelerate this query, if one was used:
If no pre-aggregations were used for this query, you should see the following screen:
Clicking takes you to the Rollup Designer, where you can add a pre-aggregation to accelerate similar queries in the future.
The tab details any activity in the query queue while processing the query. This may include other queries that were being processed or were waiting in the queue by Cube Cloud at the same time as this query:
A large number of queries in the queue may indicate that your deployment is under-provisioned, and you may want to consider scaling up your deployment.
The tab shows a flame graph of a query's execution time across resources in the Cube Cloud deployment. This is extremely useful for diagnosing where time is being spent in a query, and can help identify bottlenecks in your Cube deployment or data source.
For Database requests, the tab shows the SQL query compiled by Cube that is executed on the data source:
This can be useful for debugging queries that are failing or taking a long time, as you can copy the query and run it directly against your data source.
If the query failed, the tab will show you the error message and stacktrace:
Errors here generally indicate a problem with querying the data source. The generated SQL query can be copied from the
tab and run directly against your data source to debug the issue.The tab shows all data source-related events that occurred while the query is in the query execution queue:
Did you find this page useful?
