Skip to content

Commit 05848b0

Browse files
committed
removing duplicate clickstack section in monitoring guide
1 parent c77e935 commit 05848b0

File tree

1 file changed

+0
-10
lines changed

1 file changed

+0
-10
lines changed

docs/use-cases/observability/cloud-monitoring.md

Lines changed: 0 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -61,16 +61,6 @@ This approach respects service idling behavior, allowing for cost optimization w
6161

6262
<ObservabilityIntegrations/>
6363

64-
### ClickStack {#clickstack}
65-
66-
ClickStack is ClickHouse's recommended observability solution for deep system analysis and debugging, providing a unified platform for logs, metrics, and traces using ClickHouse as the storage engine. This approach relies on HyperDX, the ClickStack UI, connecting directly to the system tables inside your ClickHouse instance.
67-
HyperDX ships with a ClickHouse focused dashboard with tabs for Selects, Inserts, and Infrastructure. Teams can also use Lucene or SQL syntax to search system tables and logs, as well as create custom visualizations via Chart Explorer for detailed system analysis.
68-
This approach is ideal for debugging complex issues, performance analysis, and deep system introspection rather than real-time production alerting.
69-
70-
:::note
71-
Note that this approach will wake idle services as HyperDX queries the system tables directly.
72-
:::
73-
7464
### ClickStack deployment options {#clickstack-deployment}
7565

7666
- **HyperDX in Clickhouse Cloud** (private preview): HyperDX can be launched on any Clickhouse Cloud service.

0 commit comments

Comments
 (0)