From 18cff4e01b8cd5de06f0fa3a61abe3a6e399d27c Mon Sep 17 00:00:00 2001 From: Hassan Khan Date: Wed, 10 May 2023 12:24:29 +0100 Subject: [PATCH] docs(workspace): rename page to Query History and update screenshots --- .../Workspace/Inspecting-Pre-aggregations.mdx | 7 +++ docs/content/Workspace/Inspecting-Queries.mdx | 43 +++++++++++-------- 2 files changed, 32 insertions(+), 18 deletions(-) diff --git a/docs/content/Workspace/Inspecting-Pre-aggregations.mdx b/docs/content/Workspace/Inspecting-Pre-aggregations.mdx index abc5909e7ef4c..f9f8c9b182795 100644 --- a/docs/content/Workspace/Inspecting-Pre-aggregations.mdx +++ b/docs/content/Workspace/Inspecting-Pre-aggregations.mdx @@ -11,6 +11,13 @@ can see which pre-aggregations are accelerating queries, if they are [being refreshed][ref-caching-using-preaggs-refresh], along with the last 24 hours of build history. + + +Pre-Aggregations are available in Cube Cloud on +[all tiers](https://cube.dev/pricing). + + + ## Exploring pre-aggregations diff --git a/docs/content/Workspace/Inspecting-Queries.mdx b/docs/content/Workspace/Inspecting-Queries.mdx index 562e2b13c6a86..053bfb1c01060 100644 --- a/docs/content/Workspace/Inspecting-Queries.mdx +++ b/docs/content/Workspace/Inspecting-Queries.mdx @@ -1,17 +1,24 @@ --- -title: Query inspection +title: Query History permalink: /cloud/inspecting-queries category: Workspace menuOrder: 4 --- -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 +The Query History screen 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][ref-caching-gs-preaggs], how long they took to execute, and if they failed. - + + +Query History is available in Cube Cloud on +[all tiers](https://cube.dev/pricing). + + + + ## Setting the time range @@ -22,25 +29,25 @@ a time period: To go back to live mode, click : ## Exploring queries -You can switch between [queries made to the API](#api-queries) and -[queries made to connected data sources](#database-queries) by switching between -the API and Database tabs. +You can switch between [queries made to the API](#inspecting-api-queries) and +[queries made to connected data sources](#inspecting-database-queries) by +switching between the API and Database tabs. ### <--{"id" : "API and Database"}--> All Queries and Top Queries @@ -50,8 +57,8 @@ while Top Queries will show the most-frequently executed queries: ### <--{"id" : "API and Database"}--> Filtering @@ -61,8 +68,8 @@ duration, cache status, whether the query was accelerated, and by failing queries: ## Inspecting API Queries @@ -162,9 +169,9 @@ and stacktrace: Errors here generally indicate a problem with querying the data source. The -generated SQL query can be copied from the -[Query](#inspecting-database-queries-query) tab and run directly -against your data source to debug the issue. +generated SQL query can be copied from +the [Query](#inspecting-database-queries-query) tab and run +directly against your data source to debug the issue. ### <--{"id" : "Inspecting Database Queries"}--> Events