Merge branch 'main' into claude/service-map-group-by

Author: javierortiz-ch

.changeset/mcp-open-world-alert-webhook.md

@@ -0,0 +1,7 @@
+---
+'@hyperdx/api': patch
+---
+
+fix: mark the MCP `clickstack_save_webhook` and `clickstack_save_alert` tools as open-world
+
+Saved webhooks and alerts send HTTP requests to third-party endpoints, so both tools now declare `openWorldHint: true`.

.changeset/promql-label-catalog-via-clickhouse-http-api.md

@@ -0,0 +1,7 @@
+---
+'@hyperdx/api': patch
+---
+
+feat: read the MCP PromQL label catalog from ClickHouse's Prometheus HTTP API
+
+`describe_source` on a ClickHouse-backed PromQL source now lists label and metric names through the `prometheus_api_v1` handler on ClickHouse 26.9+, and falls back to SQL on older servers, servers without the handler, and sources set to `table-function`.

.changeset/promql-labels-via-clickhouse-http-api.md

@@ -0,0 +1,8 @@
+---
+'@hyperdx/api': minor
+'@hyperdx/common-utils': minor
+---
+
+feat: serve PromQL label lookups from ClickHouse's Prometheus HTTP API
+
+On ClickHouse 26.9+ with the `prometheus_api_v1` handler, `/labels` and `/label/:name/values` for a ClickHouse-backed PromQL source now proxy to the handler instead of querying the TimeSeries tags table with SQL. Older servers, servers without the handler, and sources set to `table-function` keep the SQL path, so a source that runs queries over HTTP on 26.6-26.8 still gets label autocomplete.

.changeset/promql-source-backend.md

@@ -0,0 +1,7 @@
+---
+'@hyperdx/api': patch
+'@hyperdx/app': patch
+'@hyperdx/common-utils': patch
+---
+
+feat: Choose how a PromQL source on ClickHouse is evaluated (the Prometheus HTTP API or the `prometheusQuery` table functions) instead of probing the server on every query. Without a choice the server is still probed, but the answer is now kept for 5 minutes. A source set to the HTTP API against a server that does not serve it fails with a clear error. Onboarding pins a PromQL source it detects to the HTTP API when the server serves it.

.changeset/service-health-no-verdict.md

@@ -0,0 +1,13 @@
+---
+'@hyperdx/api': patch
+---
+
+fix(mcp): drop the health verdict from clickstack_service_health
+
+The tool no longer labels services critical, degraded or healthy, and no longer
+tells agents a service needs "no action". Each service keeps its threshold
+flags, score and a factual summary, so agents reason from the numbers instead of
+a verdict that service-wide totals can get wrong. `summary.statusCounts` is
+replaced by `summary.servicesFlagged`, and the span attributes
+`mcp.service_health.critical_count` and `mcp.service_health.degraded_count` are
+replaced by `mcp.service_health.flagged_count`.

.changeset/upgrade-clickhouse-26-10.md

@@ -0,0 +1,11 @@
+---
+'@hyperdx/api': minor
+---
+
+chore: upgrade bundled ClickHouse to 26.10.3.7
+
+The all-in-one image and the Docker Compose files now use
+`clickhouse/clickhouse-server:26.10.3.7-alpine`. New TimeSeries tables default
+to schema version 8, which keeps each series' time range in a separate inner
+table; existing tables keep their layout. `system.metric_log` switches to the
+bucketed schema, and rows from before the upgrade move to `system.metric_log_0`.

agent_docs/observability.md

@@ -305,9 +305,10 @@ calls `/api/v1/prometheus/query{,_range}`, and `/labels` and
 (`QUERY_ATTRIBUTION_HEADER`), and the router parses it with `parseLogComment`
 into a `withQueryAttribution` scope layered over the auth middleware's `api`
 scope. The browser's surface and ids win; `trace` and `label` stay the
-server's. Queries the route runs through a ClickHouse client (label lookups,
-and the `prometheusQuery()`/`prometheusQueryRange()` fallback) pick the scope
-up as usual. Requests proxied to ClickHouse's Prometheus HTTP API on 26.6+ are tagged
+server's. Queries the route runs through a ClickHouse client (label lookups
+before 26.9, and the `prometheusQuery()`/`prometheusQueryRange()` fallback)
+pick the scope up as usual. Requests proxied to ClickHouse's Prometheus HTTP
+API (queries on 26.6+, label lookups on 26.9+) are tagged
 by `clickhousePrometheusRequest`: `log_comment` as a URL setting, `query_id` as
 the `X-ClickHouse-Query-Id` header, because the handler rejects `query_id` as an
 unknown setting in the URL.

docker-compose.ci.yml

@@ -22,7 +22,7 @@ services:
     depends_on:
       - ch-server
   ch-server:
-    image: clickhouse/clickhouse-server:26.8.36.3-alpine
+    image: clickhouse/clickhouse-server:26.10.3.7-alpine
     environment:
       # default settings
       CLICKHOUSE_DEFAULT_ACCESS_MANAGEMENT: 1

docker-compose.dev.yml

@@ -112,7 +112,7 @@ services:
       hdx.dev.service: clickhouse
       hdx.dev.port: '${HDX_DEV_CH_HTTP_PORT:-8123}'
       hdx.dev.url: 'http://localhost:${HDX_DEV_CH_HTTP_PORT:-8123}'
-    image: clickhouse/clickhouse-server:26.8.36.3-alpine
+    image: clickhouse/clickhouse-server:26.10.3.7-alpine
     ports:
       - '${HDX_DEV_CH_HTTP_PORT:-8123}:8123' # http api
       - '${HDX_DEV_CH_NATIVE_PORT:-9000}:9000' # native

docker-compose.yml

@@ -109,7 +109,7 @@ services:
       - ch-server
       - db
   ch-server:
-    image: clickhouse/clickhouse-server:26.8.36.3-alpine
+    image: clickhouse/clickhouse-server:26.10.3.7-alpine
     # WARNING: Exposing the database port will make it accessible from outside the container,
     # potentially allowing unauthorized access. If you uncomment the ports below,
     # ensure to secure your database (e.g., with strong authentication, proper network rules, and firewalls).