Use this file to discover all available pages before exploring further.
It provides a real-time and historic view of requests to data APIs of your
Cube Cloud deployment, so you can check whether queries were 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 navigate throughout the query history by using the date picker in the
top right corner of the page and selecting a time period:
Clicking All Queries will show all queries in order of recency,
while Top Queries will show the queries with the largest total duration (hits * avg duration) in the selected time frame. Both results are limited to 100 unique queries.
In the table, all queries are shown in their collapsed view by default.
To see an expanded view of a query, click on the ❯ button
to the left of any query.
Check the columns to see the details:
Query column shows a representation of a query, similar to the
REST (JSON) API query format. In case of the SQL API, if the
query is not coercible to a REST (JSON) API query, raw SQL is shown “as is.”
API column shows the API type that was used to run the query:
REST (JSON) API via HTTP transport, REST (JSON) API via WebSockets, GraphQL API, or SQL API.
Duration column shows how long the query took.
Bolt icon indicates the cache type that was used to
fulfill the query.
Time column shows the point in time the query was run at.
To drill down on a specific query, click it to see more information.
The Queue Graph 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 Flame Graph 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 Query 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 Errors 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 Query tab and
run directly against your data source to debug the issue.
