diff --git a/.changeset/add-click-ui.md b/.changeset/add-click-ui.md deleted file mode 100644 index 90cd8b962d..0000000000 --- a/.changeset/add-click-ui.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -'@hyperdx/app': patch ---- - -feat: add `@clickhouse/click-ui` as a dependency and mount `ClickUIProvider` -next to `MantineProvider`. The provider follows the HyperDX color mode and does -not persist its own theme. The "open an issue on GitHub" link in error messages -is the first component to use click-ui (`Link`). diff --git a/.changeset/ai-sdk-v7-genai-spans.md b/.changeset/ai-sdk-v7-genai-spans.md deleted file mode 100644 index 24e2d5ad58..0000000000 --- a/.changeset/ai-sdk-v7-genai-spans.md +++ /dev/null @@ -1,7 +0,0 @@ ---- -'@hyperdx/api': patch ---- - -feat: upgrade the AI SDK to v7 and trace AI calls with GenAI semantic conventions - -AI assistant calls now emit OpenTelemetry spans that follow the GenAI semantic conventions (`invoke_agent` / `chat` / `execute_tool` spans with `gen_ai.*` attributes) instead of the legacy `ai.*` span shape. Team and user attribution moves from `ai.telemetry.metadata.*` to `hyperdx.team.id` and `user.id` (plus `gen_ai.conversation.id` when a session is known). Saved searches, alerts or dashboards keyed on the old `ai.*` span names or attributes need updating. diff --git a/.changeset/alert-state-badge-click-ui.md b/.changeset/alert-state-badge-click-ui.md deleted file mode 100644 index ffdf486db5..0000000000 --- a/.changeset/alert-state-badge-click-ui.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -'@hyperdx/app': patch ---- - -feat: use the click-ui `Badge` for alert state badges. A fired alert shows a -solid red badge, and an evaluation error shows a light red badge. diff --git a/.changeset/dismiss-metric-drilldown-warning.md b/.changeset/dismiss-metric-drilldown-warning.md deleted file mode 100644 index 83e0e05864..0000000000 --- a/.changeset/dismiss-metric-drilldown-warning.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -'@hyperdx/app': patch ---- - -feat: let users permanently dismiss the metric drill-down warning - -Drilling down from a metric chart whose source has no correlated log source -shows a warning. Clicking its close button now hides the warning for good in -that browser, and repeated clicks no longer stack copies of it. diff --git a/.changeset/express-session-secret-no-default.md b/.changeset/express-session-secret-no-default.md deleted file mode 100644 index 7f12b91da4..0000000000 --- a/.changeset/express-session-secret-no-default.md +++ /dev/null @@ -1,12 +0,0 @@ ---- -'@hyperdx/api': minor ---- - -The API no longer falls back to the public session secret `hyperdx is cool ๐Ÿ‘‹`. -If `EXPRESS_SESSION_SECRET` is unset, the API generates a random secret and -reports it once at startup when authentication is enabled. Authenticated -deployments that explicitly set the old public value also get a random secret -and the same warning; the public value remains available only in the no-auth -local demo. Set it to a random string (`openssl rand -hex 32`) in any deployment -with authentication enabled โ€” without it, restarting the API signs every user -out, and replicas do not share sessions. diff --git a/.changeset/fixedstring-implicit-hastoken.md b/.changeset/fixedstring-implicit-hastoken.md deleted file mode 100644 index 3826b27edb..0000000000 --- a/.changeset/fixedstring-implicit-hastoken.md +++ /dev/null @@ -1,11 +0,0 @@ ---- -'@hyperdx/common-utils': patch -'@hyperdx/api': patch -'@hyperdx/app': patch ---- - -fix: cast FixedString columns before implicit hasToken search - -A bare search term against a FixedString column such as OTel TraceId compiled to -hasToken(lower(TraceId), ...), which ClickHouse rejects. Those haystacks are now -CAST to String first. diff --git a/.changeset/heatmap-granularity.md b/.changeset/heatmap-granularity.md deleted file mode 100644 index 149efe717c..0000000000 --- a/.changeset/heatmap-granularity.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -'@hyperdx/app': patch ---- - -feat: Respect explicit and minimum granularity on heatmaps diff --git a/.changeset/heatmap-hover-cell.md b/.changeset/heatmap-hover-cell.md deleted file mode 100644 index 51ee407866..0000000000 --- a/.changeset/heatmap-hover-cell.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -'@hyperdx/app': patch ---- - -fix: Match heatmap hover to the cell under the cursor diff --git a/.changeset/heatmap-inline-settings.md b/.changeset/heatmap-inline-settings.md deleted file mode 100644 index 9f56875219..0000000000 --- a/.changeset/heatmap-inline-settings.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -'@hyperdx/app': patch ---- - -feat: Edit heatmap value and count inline in the chart editor diff --git a/.changeset/heatmap-series-mode.md b/.changeset/heatmap-series-mode.md deleted file mode 100644 index d0f1d967a2..0000000000 --- a/.changeset/heatmap-series-mode.md +++ /dev/null @@ -1,7 +0,0 @@ ---- -'@hyperdx/app': minor -'@hyperdx/common-utils': minor -'@hyperdx/api': patch ---- - -feat: Add a series mode to builder heatmaps diff --git a/.changeset/inline-name-input.md b/.changeset/inline-name-input.md deleted file mode 100644 index f7cc732a8a..0000000000 --- a/.changeset/inline-name-input.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -'@hyperdx/app': patch ---- - -feat: rename dashboards and saved searches by clicking the title instead of a -pencil button - -The name is now edited in place: Enter or clicking away saves, Escape reverts. diff --git a/.changeset/instance-label-brand-name.md b/.changeset/instance-label-brand-name.md deleted file mode 100644 index 19c3ac011d..0000000000 --- a/.changeset/instance-label-brand-name.md +++ /dev/null @@ -1,7 +0,0 @@ ---- -'@hyperdx/app': patch ---- - -feat: add optional `NEXT_PUBLIC_INSTANCE_LABEL` suffix to the tab title and sidebar - -Operators running multiple HyperDX instances (e.g. one per region) can now set `NEXT_PUBLIC_INSTANCE_LABEL` to append a short label to the browser tab title and sidebar, e.g. "HyperDX UK". Empty by default, no behavior change if unset. The sidebar label only shows when the sidebar is expanded, and replaces the UTC badge there when both are set. diff --git a/.changeset/json-viewer-key-order.md b/.changeset/json-viewer-key-order.md deleted file mode 100644 index 3c57bed530..0000000000 --- a/.changeset/json-viewer-key-order.md +++ /dev/null @@ -1,13 +0,0 @@ ---- -'@hyperdx/app': patch ---- - -feat: choose how property keys are ordered in the row side panel - -The JSON viewer sorts keys alphabetically, which is the right default for wide -ClickHouse `Map(...)` columns like `ProfileEvents` but hides the stored column -order. The properties view options menu now offers "Sort keys Aโ€“Z", "Sort keys -Zโ€“A", and "Original order"; the choice persists with the viewer's other options. -Array elements keep their index order in every mode. In "Original order", -integer-like keys (e.g. HTTP status codes) still list first in ascending order, -since parsed JavaScript objects order keys that way. diff --git a/.changeset/map-keys-text-index-fallthrough.md b/.changeset/map-keys-text-index-fallthrough.md deleted file mode 100644 index ed38a7ea22..0000000000 --- a/.changeset/map-keys-text-index-fallthrough.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -'@hyperdx/common-utils': patch -'@hyperdx/app': patch -'@hyperdx/api': patch ---- - -fix: fall back to the Map key scan when the text index read fails - -`getMapKeys` returned an empty list whenever its `mergeTreeTextIndex` query -failed, so the rollup and bounded `mapKeys` scan paths never ran. ClickHouse -refuses `mergeTreeTextIndex` with `ACCESS_DENIED` on any table with a row -policy, which left search autocomplete with no Map keys on those tables. A -failed text index read now falls through to the next strategy. After a row -policy denial it skips the key rollup table, which the policy doesn't cover, -and reads keys only from the policy-filtered source table. diff --git a/.changeset/mcp-describe-source-partial-timeout.md b/.changeset/mcp-describe-source-partial-timeout.md deleted file mode 100644 index ad0344ee19..0000000000 --- a/.changeset/mcp-describe-source-partial-timeout.md +++ /dev/null @@ -1,10 +0,0 @@ ---- -'@hyperdx/api': patch ---- - -fix(mcp): return partial `clickstack_describe_source` results on timeout - -The describe deadline is raised from 10s to 30s to match the other MCP query -tools. When it is hit, the tool now returns the schema and samples gathered so -far, flagged `partial` with `skippedStages`, instead of failing outright. It -only returns a timeout error if the column schema never loaded. diff --git a/.changeset/mcp-list-metrics-speedup.md b/.changeset/mcp-list-metrics-speedup.md deleted file mode 100644 index 9305698e18..0000000000 --- a/.changeset/mcp-list-metrics-speedup.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -'@hyperdx/api': patch ---- - -perf(mcp): speed up `clickstack_list_metrics` and give the metric discovery -tools a 30s budget - -`clickstack_list_metrics` now scans metric names only (about 9x fewer bytes read -per kind), fetches unit and description just for the returned page, and scans -kinds in parallel. When the time budget runs out it returns the kinds that -finished, reports the rest in `partialFailure`, and returns a `nextCursor` that -resumes at the timed-out kind instead of failing the whole call. It also no -longer drops later kinds when one kind exactly fills a page. -`clickstack_list_metrics` and `clickstack_describe_metric` now allow 30s instead -of 10s, matching the other MCP query tools. diff --git a/.changeset/mcp-shared-timeout.md b/.changeset/mcp-shared-timeout.md deleted file mode 100644 index e412f42588..0000000000 --- a/.changeset/mcp-shared-timeout.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -'@hyperdx/api': patch ---- - -refactor(mcp): share wall-clock timeout handling across MCP tools via -`runWithTimeout`, and source the 30s ClickHouse query cap from one constant. diff --git a/.changeset/metadata-map-key-limits.md b/.changeset/metadata-map-key-limits.md deleted file mode 100644 index ad550c442d..0000000000 --- a/.changeset/metadata-map-key-limits.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -'@hyperdx/common-utils': patch ---- - -Include the requested Map-key limit in metadata cache keys so MCP discovery and AI field discovery cannot reuse each other's differently limited results. diff --git a/.changeset/plural-source-kind-labels.md b/.changeset/plural-source-kind-labels.md deleted file mode 100644 index 29156c8742..0000000000 --- a/.changeset/plural-source-kind-labels.md +++ /dev/null @@ -1,7 +0,0 @@ ---- -'@hyperdx/app': patch ---- - -fix: use plural source kind labels and "OTel" spelling on the Sources page - -The source form's data type options and the sources list now read Logs, Traces, OTel metrics, Sessions, and PromQL. diff --git a/.changeset/promql-auto-detect-source.md b/.changeset/promql-auto-detect-source.md deleted file mode 100644 index 4dc304ffc4..0000000000 --- a/.changeset/promql-auto-detect-source.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -'@hyperdx/common-utils': patch -'@hyperdx/app': patch ---- - -feat: auto-detect a PromQL source during onboarding - -When PromQL is enabled (`NEXT_PUBLIC_ENABLE_PROMQL=true`), onboarding source auto-detection now also creates a PromQL source for a ClickHouse TimeSeries engine table. It prefers `prometheus.metrics` (the table the ClickHouse Prometheus docs suggest), then a table named `metrics_ts`, and otherwise picks the only TimeSeries table on the connection. A service with only a TimeSeries table is no longer sent to manual source setup. diff --git a/.changeset/promql-default-source-gate.md b/.changeset/promql-default-source-gate.md deleted file mode 100644 index 98d1a010ed..0000000000 --- a/.changeset/promql-default-source-gate.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -'@hyperdx/api': patch ---- - -feat: only provision a default PromQL source when PromQL is enabled - -`DEFAULT_SOURCES` entries of kind `promql` are now skipped unless -`ENABLE_PROMQL=true`, so a single sources list can include a PromQL source -without creating it on deployments that have PromQL turned off. diff --git a/.changeset/promql-heatmap.md b/.changeset/promql-heatmap.md deleted file mode 100644 index 74c5acd713..0000000000 --- a/.changeset/promql-heatmap.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -'@hyperdx/app': minor ---- - -feat: Support PromQL heatmaps (series-mode) diff --git a/.changeset/promql-min-auto-granularity.md b/.changeset/promql-min-auto-granularity.md deleted file mode 100644 index 62f1b0e53c..0000000000 --- a/.changeset/promql-min-auto-granularity.md +++ /dev/null @@ -1,7 +0,0 @@ ---- -'@hyperdx/common-utils': minor -'@hyperdx/app': minor -'@hyperdx/api': patch ---- - -Support "Minimum auto granularity" on PromQL sources. It floors the step of charts on auto granularity, as it does for metric sources, and `$__rate_interval` now uses it as the source's scrape interval (still 15s when unset) instead of always assuming 15s. A granularity picked on a tile is never changed. diff --git a/.changeset/promql-query-attribution.md b/.changeset/promql-query-attribution.md deleted file mode 100644 index 7c0e0cedc9..0000000000 --- a/.changeset/promql-query-attribution.md +++ /dev/null @@ -1,7 +0,0 @@ ---- -'@hyperdx/common-utils': minor -'@hyperdx/api': minor -'@hyperdx/app': minor ---- - -feat: Attribute PromQL queries to the dashboard, tile or search that issued them, through both the `prometheusQuery`/`prometheusQueryRange` table functions and ClickHouse's Prometheus HTTP API diff --git a/.changeset/promql-series-limit.md b/.changeset/promql-series-limit.md deleted file mode 100644 index 50be3a9bc5..0000000000 --- a/.changeset/promql-series-limit.md +++ /dev/null @@ -1,7 +0,0 @@ ---- -'@hyperdx/app': patch ---- - -feat: support a series limit on PromQL line, stacked bar, pie and bar charts - -The Display Settings drawer now offers Series Limit for PromQL charts. On line and stacked bar charts it keeps the top N series by peak value (leave empty for the default of 250, or set 0 for unlimited). On pie and bar charts it keeps the N largest slices or bars (leave empty to show all). diff --git a/.changeset/promql-variable-format.md b/.changeset/promql-variable-format.md deleted file mode 100644 index a11479ad5b..0000000000 --- a/.changeset/promql-variable-format.md +++ /dev/null @@ -1,7 +0,0 @@ ---- -'@hyperdx/common-utils': patch -'@hyperdx/api': patch -'@hyperdx/app': patch ---- - -feat: Add a promql variable format that escapes based on single/multi-select diff --git a/.changeset/proud-walls-argue.md b/.changeset/proud-walls-argue.md deleted file mode 100644 index 6ad800b8f6..0000000000 --- a/.changeset/proud-walls-argue.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -"@hyperdx/api": patch ---- - -feat: Support series mode heatmap in API and MCP diff --git a/.changeset/query-log-attribution.md b/.changeset/query-log-attribution.md deleted file mode 100644 index f11020165d..0000000000 --- a/.changeset/query-log-attribution.md +++ /dev/null @@ -1,40 +0,0 @@ ---- -'@hyperdx/common-utils': minor -'@hyperdx/api': minor -'@hyperdx/app': minor ---- - -feat: attribute ClickHouse queries to the dashboard, tile, search or alert that -issued them - -A row in `system.query_log` previously couldn't be attributed to the part of -HyperDX that produced it. Now every query HyperDX runs has a small JSON -`log_comment`, plus a `query_id` starting with `hdx-`. - -Attribute load after the fact: - -```sql -SELECT - JSONExtractString(log_comment, 'surface') AS surface, - JSONExtractString(log_comment, 'dashboard') AS dashboard, - JSONExtractString(log_comment, 'tile') AS tile, - count(), - sum(read_rows) -FROM system.query_log -WHERE type = 'QueryFinish' AND log_comment != '' AND query_id like 'hdx-%' -GROUP BY ALL -ORDER BY sum(read_rows) DESC -``` - -Or spot a query while it is still running, in `system.processes`, where the -`query_id` names the surface with no JSON parsing needed. - -The payload records which part of the product asked (a dashboard, a search, an -alert, an MCP tool, the chart explorer, session replay, field lookups, and so -on), the dashboard and tile or saved search id, the source id, and on the server -the trace id of the request. Field lookups and autocomplete are labelled too, so -they can be told apart from a user's chart queries. - -The exception is queries that skip settings processing: the `system.settings`, -server version and Cloud-detection probes, and the onboarding connection check. -They get a `query_id` but an empty `log_comment`. diff --git a/.changeset/services-tiles-refresh-pulse.md b/.changeset/services-tiles-refresh-pulse.md deleted file mode 100644 index c3ecf6c2a8..0000000000 --- a/.changeset/services-tiles-refresh-pulse.md +++ /dev/null @@ -1,11 +0,0 @@ ---- -'@hyperdx/app': patch ---- - -fix: pulse the list-bar and histogram charts while they refresh - -The Services dashboard's list-bar and latency histogram charts kept their -previous data during a refresh but gave no sign that new data was loading, -and the histogram could briefly swap its chart for "Loading Chart Data...". -Both now keep their previous data on screen and pulse while the refetch runs, -like the other charts. diff --git a/.changeset/single-select-dashboard-filters.md b/.changeset/single-select-dashboard-filters.md deleted file mode 100644 index 150f0458cc..0000000000 --- a/.changeset/single-select-dashboard-filters.md +++ /dev/null @@ -1,7 +0,0 @@ ---- -'@hyperdx/common-utils': patch -'@hyperdx/api': patch -'@hyperdx/app': patch ---- - -feat: Allow configuring dashboard filters as single-select diff --git a/.changeset/stacked-line-charts.md b/.changeset/stacked-line-charts.md deleted file mode 100644 index 6392189e2a..0000000000 --- a/.changeset/stacked-line-charts.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -'@hyperdx/common-utils': minor -'@hyperdx/app': minor -'@hyperdx/api': minor -'@hyperdx/cli': minor ---- - -feat: add stacked line (stacked area) time-series display type diff --git a/.changeset/text-index-key-order.md b/.changeset/text-index-key-order.md deleted file mode 100644 index b3af9ae7ec..0000000000 --- a/.changeset/text-index-key-order.md +++ /dev/null @@ -1,13 +0,0 @@ ---- -'@hyperdx/common-utils': patch -'@hyperdx/app': patch -'@hyperdx/api': patch ---- - -fix: rank Map keys by frequency when a text index serves key discovery - -The two `mergeTreeTextIndex` paths in `getMapKeys` grouped keys and applied -`LIMIT maxKeys` with no `ORDER BY`, so on a column with more keys than the -limit the filter sidebar showed an arbitrary subset. They now order by -`sum(cardinality) DESC, key`, which keeps the most frequent keys, as the key -rollup path already does with `sum(count) DESC`. diff --git a/.changeset/trace-breakdown-timeout.md b/.changeset/trace-breakdown-timeout.md deleted file mode 100644 index 26c435b3f9..0000000000 --- a/.changeset/trace-breakdown-timeout.md +++ /dev/null @@ -1,12 +0,0 @@ ---- -'@hyperdx/api': patch ---- - -fix(mcp): time-limit the `clickstack_trace_top_time_consuming_operations` tool. -Its queries now use the MCP request timeout and `max_execution_time` ceiling, -which a source's `querySettings` can no longer override. A timeout returns -guidance to shorten the window or narrow `parentFilter` instead of an "invalid -SQL" hint, and the client-side `Timeout error.` now gets the timeout hint in -every MCP tool. Sources with a multi-column `timestampValueExpression` -(including a leading Date column such as `EventDate, EventTime`) now return -correct breakdowns. diff --git a/.changeset/trace-total-duration-search-table.md b/.changeset/trace-total-duration-search-table.md deleted file mode 100644 index d550e91230..0000000000 --- a/.changeset/trace-total-duration-search-table.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -'@hyperdx/app': patch ---- - -feat: show a trace's total wall-clock duration in the waterfall controls bar \ No newline at end of file diff --git a/.changeset/violet-onions-tickle.md b/.changeset/violet-onions-tickle.md deleted file mode 100644 index 10ea5afa3d..0000000000 --- a/.changeset/violet-onions-tickle.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -"@hyperdx/app": patch ---- - -ui: Extract FilterPill, add filter editor components diff --git a/.env b/.env index 69ee2caa60..2abe530b1b 100644 --- a/.env +++ b/.env @@ -8,8 +8,8 @@ NEXT_ALL_IN_ONE_IMAGE_NAME_DOCKERHUB=clickhouse/clickstack-all-in-one ALL_IN_ONE_IMAGE_NAME_DOCKERHUB=hyperdx/hyperdx-all-in-one NEXT_OTEL_COLLECTOR_IMAGE_NAME_DOCKERHUB=clickhouse/clickstack-otel-collector OTEL_COLLECTOR_IMAGE_NAME_DOCKERHUB=hyperdx/hyperdx-otel-collector -CODE_VERSION=2.40.0 -IMAGE_VERSION_SUB_TAG=.40.0 +CODE_VERSION=2.41.0 +IMAGE_VERSION_SUB_TAG=.41.0 IMAGE_VERSION=2 IMAGE_NIGHTLY_TAG=2-nightly IMAGE_LATEST_TAG=latest diff --git a/CHANGELOG.md b/CHANGELOG.md index 441e54a7f1..136b6cfa00 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -6,6 +6,239 @@ PR โ€” keep the `hyperdx-release-notes` comment marker intact when editing so yo edits survive regeneration. Per-package detail lives in each `packages/*/CHANGELOG.md`. +## v2.41.0 โ€” 2026-10-09 + + + +**Query attribution and a session secret change** + +Every ClickHouse query HyperDX runs โ€” PromQL included โ€” is now tagged with the +part of the product that issued it, so a row in `system.query_log` tells you +which dashboard, tile, search or alert put that load on your cluster. PromQL +sources also pick up the "Minimum auto granularity" setting that metric sources +already had, so charts left on auto granularity stop inferring buckets finer +than your scrape interval. This release also restores Map attribute +autocomplete on tables guarded by a ClickHouse row policy, where the search bar +and the chart, alert and dashboard-filter editors had stopped suggesting any +keys at all. If you run HyperDX with authentication enabled, set +`EXPRESS_SESSION_SECRET` before upgrading โ€” the API no longer falls back to a +public default secret. + +### ๐Ÿ’ฅ Breaking Changes + +- **The API no longer signs sessions with a public default secret**: + `EXPRESS_SESSION_SECRET` used to fall back to the public value `hyperdx is + cool ๐Ÿ‘‹`. With authentication enabled, leaving it unset โ€” or setting it + explicitly to that old public value โ€” now gets a random secret generated at + startup and reported once in the logs, which means restarting the API signs + every user out and replicas do not share sessions between them. Set it to a + random string (`openssl rand -hex 32`) in any deployment with authentication + enabled; the public value remains available only in the no-auth local demo + (#3129, thanks @28Hus!). +- **AI assistant calls are traced with the GenAI semantic conventions**: with + the AI SDK upgraded to v7, HyperDX now emits `invoke_agent`, `chat` and + `execute_tool` spans carrying `gen_ai.*` attributes in place of the legacy + `ai.*` span shape, and team and user attribution moves from + `ai.telemetry.metadata.*` to `hyperdx.team.id` and `user.id`, plus + `gen_ai.conversation.id` when a session is known. Update any saved search, + alert or dashboard keyed on the old `ai.*` span names or attributes (#3261). + +### โœจ New Features + +- **Attribute ClickHouse queries to the dashboard, search or alert behind + them**: every query HyperDX issues now carries a small JSON `log_comment` and + a `query_id` beginning with `hdx-`, naming the surface that asked โ€” a + dashboard and tile, a saved search, an alert, an MCP tool, the chart explorer, + session replay or a field lookup โ€” along with the source id and, from the + server, the trace id of the request. Group `system.query_log` by + `JSONExtractString(log_comment, 'surface')` to see where your read load + actually goes, or read the `query_id` straight out of `system.processes` to + name a query while it is still running, with no JSON parsing needed. PromQL + queries are attributed the same way, whether they run through the + `prometheusQuery`/`prometheusQueryRange` table functions or ClickHouse's + Prometheus HTTP API, so a PromQL-backed dashboard, tile or search shows up in + the same accounting as the rest. The exception is the probes that skip + settings processing โ€” the `system.settings`, server version and + Cloud-detection checks, and the onboarding connection test โ€” which get a + `query_id` but an empty `log_comment` (#3155, #3300, thanks @tommyzli!). +- **Minimum auto granularity on PromQL sources**: a PromQL source can now set a + "Minimum auto granularity", as a metric source already could, and it floors + the step of any chart left on auto granularity so a short date range cannot + infer buckets finer than your metrics actually arrive. `$__rate_interval` now + takes that value as the source's scrape interval instead of always assuming + 15s โ€” still 15s when the setting is left unset โ€” and a granularity you choose + explicitly on a tile is never changed (#3292, thanks @karl-power!). +- **A series limit for PromQL charts**: the Display Settings drawer now offers a + Series Limit on PromQL line, stacked bar, pie and bar charts, so a query that + fans out over hundreds of series stays readable. Line and stacked bar charts + keep the top N series by peak value โ€” leave it empty for the default of 250, + or set 0 for unlimited โ€” while pie and bar charts keep the N largest slices or + bars, and show all of them when it is left empty (#3294, thanks + @karl-power!). +- **A series mode for builder heatmaps**: a heatmap built in the chart builder + now offers a series mode, so the tile can be driven by the series your query + returns rather than only by the single distribution it plotted before. The API + and the MCP tools understand the new mode too, so a heatmap saved with it + renders and queries the same way outside the app. A PromQL source can drive a + series-mode heatmap as well, so a PromQL query's series can be read as a + heatmap rather than only as lines (#3291, #3298, #3313, thanks @pulpdrew!). +- **Stacked line charts**: time series tiles gain a stacked line (stacked area) + display type, so a set of series can be read as a total and its composition + on one chart rather than as separate lines you add up by eye. The app, the + API and the CLI all understand the new display type (#3290, thanks + @pulpdrew!). +- **Single-select dashboard filters**: a dashboard filter can now be configured + to take one value at a time instead of a set, so a filter that is only ever + meant to scope the dashboard to a single value behaves that way for everyone + using it (#3295, thanks @pulpdrew!). +- **A PromQL variable format that escapes to suit the filter**: a dashboard + variable used in a PromQL expression now has a `promql` format that escapes + its value according to whether the filter it comes from is single- or + multi-select, so one expression holds up whether the variable resolves to a + single value or to several (#3297, thanks @pulpdrew!). +- **Choose how property keys are ordered in the row side panel**: the JSON + viewer sorts keys alphabetically, which is the right default for a wide + ClickHouse `Map(...)` column such as `ProfileEvents` but hides the order the + columns are stored in. The properties view options menu now offers "Sort keys + Aโ€“Z", "Sort keys Zโ€“A" and "Original order", and your choice persists with the + viewer's other options. Array elements keep their index order in every mode, + and in "Original order" integer-like keys โ€” HTTP status codes, say โ€” still + list first in ascending order, since that is how parsed JavaScript objects + order their keys (#3126, thanks @MikeShi42!). +- **Label each instance in the tab title and sidebar**: operators running more + than one HyperDX โ€” one per region, say โ€” can now set + `NEXT_PUBLIC_INSTANCE_LABEL` to a short label such as "UK", which is appended + to the browser tab title and shown in the sidebar, so a wall of tabs tells you + which instance you are looking at. It is empty by default and changes nothing + unless you set it; the sidebar shows the label only while the sidebar is + expanded, where it takes the place of the UTC badge when both are set (#3250, + thanks @arj22!). + +### ๐Ÿงช Experimental + +- **Onboarding detects a PromQL source for you**: with PromQL enabled + (`NEXT_PUBLIC_ENABLE_PROMQL=true`), onboarding's source auto-detection now + also creates a PromQL source for a ClickHouse TimeSeries engine table. It + prefers `prometheus.metrics`, the table the ClickHouse Prometheus docs + suggest, then one named `metrics_ts`, and otherwise takes the only TimeSeries + table on the connection โ€” and a service that has nothing but a TimeSeries + table is no longer sent off to manual source setup (#3310, thanks + @karl-power!). +- **A default PromQL source is provisioned only where PromQL is on**: a + `DEFAULT_SOURCES` entry of kind `promql` is now skipped unless + `ENABLE_PROMQL=true`, so one sources list can carry a PromQL source and still + be used on deployments that have PromQL turned off, where it simply is not + created (#3311, thanks @karl-power!). + +### ๐Ÿ”ง Improvements + +- **A trace's total duration in the waterfall controls bar**: the trace + waterfall now shows how long the whole trace took in wall-clock terms, right + in its controls bar, so you can size up a trace without reading it off the + timeline (#3051, thanks @milansanjeev!). +- **Heatmaps respect explicit and minimum granularity**: a heatmap now honours + the granularity you set on the tile, and the minimum auto granularity its + source carries, when it buckets time, rather than choosing its own interval + regardless (#3305, thanks @pulpdrew!). +- **Heatmap value and count edited in the chart editor**: a heatmap's value and + count inputs now sit inline in the chart editor form, alongside the rest of + the tile's settings, rather than apart from them (#3277, thanks @pulpdrew!). +- **Rename a dashboard or saved search by clicking its title**: the pencil + button is gone โ€” click the name where it sits to edit it in place, with Enter + or a click away to save and Escape to revert (#3278, thanks @elizabetdev!). +- **The metric drill-down warning can be dismissed for good**: drilling down + from a metric chart whose source has no correlated log source shows a warning, + and closing it now hides it permanently in that browser instead of having it + return on the next drill-down. Clicking through several times no longer stacks + copies of the warning either (#3304, thanks @knudtty!). +- **`clickstack_list_metrics` is faster and no longer fails at the deadline**: + the MCP metric listing scans metric names only โ€” about 9x fewer bytes read per + kind โ€” fetches unit and description just for the page it returns, and scans + kinds in parallel. When the time budget runs out it returns the kinds that + finished, reports the rest in `partialFailure`, and hands back a `nextCursor` + that resumes at the kind that timed out instead of failing the whole call; it + also stops dropping later kinds when one kind exactly fills a page. Both + `clickstack_list_metrics` and `clickstack_describe_metric` now get 30s rather + than 10s, matching the other MCP query tools (#3260). + +### ๐Ÿ› Bug Fixes + +- **Map key autocomplete works again on tables with a row policy**: ClickHouse + refuses the `mergeTreeTextIndex` lookup with `ACCESS_DENIED` on any table + carrying a row policy, and key discovery treated that as "no keys" rather than + trying anything else, so autocomplete offered nothing for `Map` columns such + as `ResourceAttributes` on those tables. A failed text index read now falls + through to the remaining strategies, reading keys from the policy-filtered + source table and skipping the key rollup table the policy does not cover + (#3268). +- **The filter sidebar keeps the Map keys you are most likely to want**: where a + text index serves key discovery, the keys were grouped and cut off at the + limit with no ordering at all, so a `Map` column holding more keys than the + limit showed an arbitrary subset of them. Both of those paths now order by + `sum(cardinality) DESC`, keeping the most frequent keys, as the key rollup + path already did (#3254, thanks @BilalAtique!). +- **Map key lookups stop serving one caller another's shortened list**: the + metadata cache keyed a column's Map keys without recording how many had been + asked for, so MCP discovery and the AI assistant's field discovery, which + request different numbers of keys, could each be handed the other's cached + answer and work from fewer keys than they asked for. The requested limit is + now part of the cache key (#3339, thanks @qoega!). +- **Plain searches against a FixedString column such as a trace id run again**: + a bare search term compiled to `hasToken(lower(TraceId), ...)`, which + ClickHouse rejects on a FixedString column, so searching an OTel TraceId + errored instead of returning the rows. Those haystacks are now cast to + `String` first (#3271, thanks @milansanjeev!). +- **Heatmap hover follows the cell under the cursor**: hovering a heatmap now + highlights and describes the cell you are actually pointing at, instead of a + neighbouring one (#3273, thanks @pulpdrew!). +- **Services charts show that they are refreshing**: the Services dashboard's + list-bar and latency histogram charts kept their previous data through a + refresh with no sign that anything was loading, and the histogram could flash + "Loading Chart Data..." in place of the chart. Both now hold their data on + screen and pulse while the refetch runs, like every other chart + (#3229, thanks @Harshul1484!). +- **Consistent source kind labels on the Sources page**: the source form's data + type options and the sources list now read Logs, Traces, OTel metrics, + Sessions and PromQL, so the names match between the two and "OTel" is spelt + the same way everywhere (#3257, thanks @teeohhem!). +- **`clickstack_describe_source` returns partial results instead of timing + out**: the MCP describe deadline is now 30s, matching the other MCP query + tools, and hitting it no longer throws away the work. The tool returns the + schema and samples it managed to gather, marked `partial` with the + `skippedStages` it had to drop, and only reports a timeout error when the + column schema never loaded at all (#3259). +- **The trace breakdown tool stops at the MCP timeout and says why**: + `clickstack_trace_top_time_consuming_operations` now runs its queries under + the MCP request timeout and its `max_execution_time` ceiling, which a source's + `querySettings` can no longer override, so the tool can no longer hang past + the deadline. A timeout now comes back with guidance to shorten the window or + narrow `parentFilter` rather than a misleading "invalid SQL" hint, and the + client-side `Timeout error.` carries that hint in every MCP tool. Sources + whose `timestampValueExpression` spans several columns, including a leading + Date column such as `EventDate, EventTime`, also return correct breakdowns + now (#3258). + +### ๐Ÿ“ฆ Build / Packaging + +- **The app bundles ClickHouse's click-ui design system**: `ClickUIProvider` is + now mounted alongside the existing Mantine provider, following HyperDX's own + colour mode rather than persisting a theme of its own. The "open an issue on + GitHub" link in error messages and the alert state badges are the first + components built on it โ€” a fired alert now shows a solid red badge and an + evaluation error a light red one (#3262, #3314, thanks @hoorayimhelping!). + + + +### ๐Ÿ“ฆ Package changelogs + +- `@hyperdx/api` 2.40.0 โ†’ 2.41.0 โ€” [changelog](https://github.com/hyperdxio/hyperdx/blob/main/packages/api/CHANGELOG.md#2410) +- `@hyperdx/app` 2.40.0 โ†’ 2.41.0 โ€” [changelog](https://github.com/hyperdxio/hyperdx/blob/main/packages/app/CHANGELOG.md#2410) +- `@hyperdx/cli` 0.6.4 โ†’ 0.7.0 โ€” [changelog](https://github.com/hyperdxio/hyperdx/blob/main/packages/cli/CHANGELOG.md#070) +- `@hyperdx/common-utils` 0.30.0 โ†’ 0.31.0 โ€” [changelog](https://github.com/hyperdxio/hyperdx/blob/main/packages/common-utils/CHANGELOG.md#0310) +- `@hyperdx/otel-collector` 2.40.0 โ†’ 2.41.0 โ€” [changelog](https://github.com/hyperdxio/hyperdx/blob/main/packages/otel-collector/CHANGELOG.md#2410) + + + ## v2.40.0 โ€” 2026-10-01 diff --git a/packages/api/CHANGELOG.md b/packages/api/CHANGELOG.md index 06edbc42d3..9519e5e9f2 100644 --- a/packages/api/CHANGELOG.md +++ b/packages/api/CHANGELOG.md @@ -1,5 +1,139 @@ # @hyperdx/api +## 2.41.0 + +### Minor Changes + +- 76d33d73: The API no longer falls back to the public session secret `hyperdx is cool ๐Ÿ‘‹`. + If `EXPRESS_SESSION_SECRET` is unset, the API generates a random secret and + reports it once at startup when authentication is enabled. Authenticated + deployments that explicitly set the old public value also get a random secret + and the same warning; the public value remains available only in the no-auth + local demo. Set it to a random string (`openssl rand -hex 32`) in any deployment + with authentication enabled โ€” without it, restarting the API signs every user + out, and replicas do not share sessions. +- d8b1cdfa: feat: Attribute PromQL queries to the dashboard, tile or search that issued them, through both the `prometheusQuery`/`prometheusQueryRange` table functions and ClickHouse's Prometheus HTTP API +- ab703243: feat: attribute ClickHouse queries to the dashboard, tile, search or alert that + issued them + + A row in `system.query_log` previously couldn't be attributed to the part of + HyperDX that produced it. Now every query HyperDX runs has a small JSON + `log_comment`, plus a `query_id` starting with `hdx-`. + + Attribute load after the fact: + + ```sql + SELECT + JSONExtractString(log_comment, 'surface') AS surface, + JSONExtractString(log_comment, 'dashboard') AS dashboard, + JSONExtractString(log_comment, 'tile') AS tile, + count(), + sum(read_rows) + FROM system.query_log + WHERE type = 'QueryFinish' AND log_comment != '' AND query_id like 'hdx-%' + GROUP BY ALL + ORDER BY sum(read_rows) DESC + ``` + + Or spot a query while it is still running, in `system.processes`, where the + `query_id` names the surface with no JSON parsing needed. + + The payload records which part of the product asked (a dashboard, a search, an + alert, an MCP tool, the chart explorer, session replay, field lookups, and so + on), the dashboard and tile or saved search id, the source id, and on the server + the trace id of the request. Field lookups and autocomplete are labelled too, so + they can be told apart from a user's chart queries. + + The exception is queries that skip settings processing: the `system.settings`, + server version and Cloud-detection probes, and the onboarding connection check. + They get a `query_id` but an empty `log_comment`. + +- 68082b67: feat: add stacked line (stacked area) time-series display type + +### Patch Changes + +- 14003f08: feat: upgrade the AI SDK to v7 and trace AI calls with GenAI semantic conventions + + AI assistant calls now emit OpenTelemetry spans that follow the GenAI semantic conventions (`invoke_agent` / `chat` / `execute_tool` spans with `gen_ai.*` attributes) instead of the legacy `ai.*` span shape. Team and user attribution moves from `ai.telemetry.metadata.*` to `hyperdx.team.id` and `user.id` (plus `gen_ai.conversation.id` when a session is known). Saved searches, alerts or dashboards keyed on the old `ai.*` span names or attributes need updating. + +- 07c93656: fix: cast FixedString columns before implicit hasToken search + + A bare search term against a FixedString column such as OTel TraceId compiled to + hasToken(lower(TraceId), ...), which ClickHouse rejects. Those haystacks are now + CAST to String first. + +- 6873416d: feat: Add a series mode to builder heatmaps +- 0b855534: fix: fall back to the Map key scan when the text index read fails + + `getMapKeys` returned an empty list whenever its `mergeTreeTextIndex` query + failed, so the rollup and bounded `mapKeys` scan paths never ran. ClickHouse + refuses `mergeTreeTextIndex` with `ACCESS_DENIED` on any table with a row + policy, which left search autocomplete with no Map keys on those tables. A + failed text index read now falls through to the next strategy. After a row + policy denial it skips the key rollup table, which the policy doesn't cover, + and reads keys only from the policy-filtered source table. + +- c2e21cf5: fix(mcp): return partial `clickstack_describe_source` results on timeout + + The describe deadline is raised from 10s to 30s to match the other MCP query + tools. When it is hit, the tool now returns the schema and samples gathered so + far, flagged `partial` with `skippedStages`, instead of failing outright. It + only returns a timeout error if the column schema never loaded. + +- cf5b831f: perf(mcp): speed up `clickstack_list_metrics` and give the metric discovery + tools a 30s budget + + `clickstack_list_metrics` now scans metric names only (about 9x fewer bytes read + per kind), fetches unit and description just for the returned page, and scans + kinds in parallel. When the time budget runs out it returns the kinds that + finished, reports the rest in `partialFailure`, and returns a `nextCursor` that + resumes at the timed-out kind instead of failing the whole call. It also no + longer drops later kinds when one kind exactly fills a page. + `clickstack_list_metrics` and `clickstack_describe_metric` now allow 30s instead + of 10s, matching the other MCP query tools. + +- 7aeb6215: refactor(mcp): share wall-clock timeout handling across MCP tools via + `runWithTimeout`, and source the 30s ClickHouse query cap from one constant. +- 6ea5f52c: feat: only provision a default PromQL source when PromQL is enabled + + `DEFAULT_SOURCES` entries of kind `promql` are now skipped unless + `ENABLE_PROMQL=true`, so a single sources list can include a PromQL source + without creating it on deployments that have PromQL turned off. + +- ff5befa8: Support "Minimum auto granularity" on PromQL sources. It floors the step of charts on auto granularity, as it does for metric sources, and `$__rate_interval` now uses it as the source's scrape interval (still 15s when unset) instead of always assuming 15s. A granularity picked on a tile is never changed. +- 1be9de8f: feat: Add a promql variable format that escapes based on single/multi-select +- 837c6837: feat: Support series mode heatmap in API and MCP +- 0d2425d5: feat: Allow configuring dashboard filters as single-select +- 1ce8b88e: fix: rank Map keys by frequency when a text index serves key discovery + + The two `mergeTreeTextIndex` paths in `getMapKeys` grouped keys and applied + `LIMIT maxKeys` with no `ORDER BY`, so on a column with more keys than the + limit the filter sidebar showed an arbitrary subset. They now order by + `sum(cardinality) DESC, key`, which keeps the most frequent keys, as the key + rollup path already does with `sum(count) DESC`. + +- e88cf3d5: fix(mcp): time-limit the `clickstack_trace_top_time_consuming_operations` tool. + Its queries now use the MCP request timeout and `max_execution_time` ceiling, + which a source's `querySettings` can no longer override. A timeout returns + guidance to shorten the window or narrow `parentFilter` instead of an "invalid + SQL" hint, and the client-side `Timeout error.` now gets the timeout hint in + every MCP tool. Sources with a multi-column `timestampValueExpression` + (including a leading Date column such as `EventDate, EventTime`) now return + correct breakdowns. +- Updated dependencies [07c93656] +- Updated dependencies [6873416d] +- Updated dependencies [0b855534] +- Updated dependencies [0846f3b2] +- Updated dependencies [e61461be] +- Updated dependencies [ff5befa8] +- Updated dependencies [d8b1cdfa] +- Updated dependencies [1be9de8f] +- Updated dependencies [ab703243] +- Updated dependencies [0d2425d5] +- Updated dependencies [68082b67] +- Updated dependencies [1ce8b88e] + - @hyperdx/common-utils@0.31.0 + ## 2.40.0 ### Minor Changes diff --git a/packages/api/package.json b/packages/api/package.json index a905c26b18..08270526ee 100644 --- a/packages/api/package.json +++ b/packages/api/package.json @@ -1,6 +1,6 @@ { "name": "@hyperdx/api", - "version": "2.40.0", + "version": "2.41.0", "license": "MIT", "private": true, "engines": { @@ -22,7 +22,7 @@ "@braintree/sanitize-url": "^7.1.1", "@clickhouse/client-common": "1.23.0-head.fae5998.1", "@esm2cjs/p-queue": "^7.3.0", - "@hyperdx/common-utils": "^0.30.0", + "@hyperdx/common-utils": "^0.31.0", "@hyperdx/node-opentelemetry": "^0.9.0", "@hyperdx/passport-local-mongoose": "^9.0.1", "@modelcontextprotocol/sdk": "^1.27.1", diff --git a/packages/app/CHANGELOG.md b/packages/app/CHANGELOG.md index 80dc09437c..573b6faac8 100644 --- a/packages/app/CHANGELOG.md +++ b/packages/app/CHANGELOG.md @@ -1,5 +1,157 @@ # @hyperdx/app +## 2.41.0 + +### Minor Changes + +- 6873416d: feat: Add a series mode to builder heatmaps +- eeabaebe: feat: Support PromQL heatmaps (series-mode) +- ff5befa8: Support "Minimum auto granularity" on PromQL sources. It floors the step of charts on auto granularity, as it does for metric sources, and `$__rate_interval` now uses it as the source's scrape interval (still 15s when unset) instead of always assuming 15s. A granularity picked on a tile is never changed. +- d8b1cdfa: feat: Attribute PromQL queries to the dashboard, tile or search that issued them, through both the `prometheusQuery`/`prometheusQueryRange` table functions and ClickHouse's Prometheus HTTP API +- ab703243: feat: attribute ClickHouse queries to the dashboard, tile, search or alert that + issued them + + A row in `system.query_log` previously couldn't be attributed to the part of + HyperDX that produced it. Now every query HyperDX runs has a small JSON + `log_comment`, plus a `query_id` starting with `hdx-`. + + Attribute load after the fact: + + ```sql + SELECT + JSONExtractString(log_comment, 'surface') AS surface, + JSONExtractString(log_comment, 'dashboard') AS dashboard, + JSONExtractString(log_comment, 'tile') AS tile, + count(), + sum(read_rows) + FROM system.query_log + WHERE type = 'QueryFinish' AND log_comment != '' AND query_id like 'hdx-%' + GROUP BY ALL + ORDER BY sum(read_rows) DESC + ``` + + Or spot a query while it is still running, in `system.processes`, where the + `query_id` names the surface with no JSON parsing needed. + + The payload records which part of the product asked (a dashboard, a search, an + alert, an MCP tool, the chart explorer, session replay, field lookups, and so + on), the dashboard and tile or saved search id, the source id, and on the server + the trace id of the request. Field lookups and autocomplete are labelled too, so + they can be told apart from a user's chart queries. + + The exception is queries that skip settings processing: the `system.settings`, + server version and Cloud-detection probes, and the onboarding connection check. + They get a `query_id` but an empty `log_comment`. + +- 68082b67: feat: add stacked line (stacked area) time-series display type + +### Patch Changes + +- 766a3b08: feat: add `@clickhouse/click-ui` as a dependency and mount `ClickUIProvider` + next to `MantineProvider`. The provider follows the HyperDX color mode and does + not persist its own theme. The "open an issue on GitHub" link in error messages + is the first component to use click-ui (`Link`). +- a986a03b: feat: use the click-ui `Badge` for alert state badges. A fired alert shows a + solid red badge, and an evaluation error shows a light red badge. +- 46ff1fc4: feat: let users permanently dismiss the metric drill-down warning + + Drilling down from a metric chart whose source has no correlated log source + shows a warning. Clicking its close button now hides the warning for good in + that browser, and repeated clicks no longer stack copies of it. + +- 07c93656: fix: cast FixedString columns before implicit hasToken search + + A bare search term against a FixedString column such as OTel TraceId compiled to + hasToken(lower(TraceId), ...), which ClickHouse rejects. Those haystacks are now + CAST to String first. + +- 3e34efa0: feat: Respect explicit and minimum granularity on heatmaps +- 3615f122: fix: Match heatmap hover to the cell under the cursor +- bd0da16c: feat: Edit heatmap value and count inline in the chart editor +- 51e47b12: feat: rename dashboards and saved searches by clicking the title instead of a + pencil button + + The name is now edited in place: Enter or clicking away saves, Escape reverts. + +- 0c1dd866: feat: add optional `NEXT_PUBLIC_INSTANCE_LABEL` suffix to the tab title and sidebar + + Operators running multiple HyperDX instances (e.g. one per region) can now set `NEXT_PUBLIC_INSTANCE_LABEL` to append a short label to the browser tab title and sidebar, e.g. "HyperDX UK". Empty by default, no behavior change if unset. The sidebar label only shows when the sidebar is expanded, and replaces the UTC badge there when both are set. + +- 01ea7f32: feat: choose how property keys are ordered in the row side panel + + The JSON viewer sorts keys alphabetically, which is the right default for wide + ClickHouse `Map(...)` columns like `ProfileEvents` but hides the stored column + order. The properties view options menu now offers "Sort keys Aโ€“Z", "Sort keys + Zโ€“A", and "Original order"; the choice persists with the viewer's other options. + Array elements keep their index order in every mode. In "Original order", + integer-like keys (e.g. HTTP status codes) still list first in ascending order, + since parsed JavaScript objects order keys that way. + +- 0b855534: fix: fall back to the Map key scan when the text index read fails + + `getMapKeys` returned an empty list whenever its `mergeTreeTextIndex` query + failed, so the rollup and bounded `mapKeys` scan paths never ran. ClickHouse + refuses `mergeTreeTextIndex` with `ACCESS_DENIED` on any table with a row + policy, which left search autocomplete with no Map keys on those tables. A + failed text index read now falls through to the next strategy. After a row + policy denial it skips the key rollup table, which the policy doesn't cover, + and reads keys only from the policy-filtered source table. + +- 0ddfe7d7: fix: use plural source kind labels and "OTel" spelling on the Sources page + + The source form's data type options and the sources list now read Logs, Traces, OTel metrics, Sessions, and PromQL. + +- e61461be: feat: auto-detect a PromQL source during onboarding + + When PromQL is enabled (`NEXT_PUBLIC_ENABLE_PROMQL=true`), onboarding source auto-detection now also creates a PromQL source for a ClickHouse TimeSeries engine table. It prefers `prometheus.metrics` (the table the ClickHouse Prometheus docs suggest), then a table named `metrics_ts`, and otherwise picks the only TimeSeries table on the connection. A service with only a TimeSeries table is no longer sent to manual source setup. + +- 76e5cf78: feat: support a series limit on PromQL line, stacked bar, pie and bar charts + + The Display Settings drawer now offers Series Limit for PromQL charts. On line and stacked bar charts it keeps the top N series by peak value (leave empty for the default of 250, or set 0 for unlimited). On pie and bar charts it keeps the N largest slices or bars (leave empty to show all). + +- 1be9de8f: feat: Add a promql variable format that escapes based on single/multi-select +- c372a71c: fix: pulse the list-bar and histogram charts while they refresh + + The Services dashboard's list-bar and latency histogram charts kept their + previous data during a refresh but gave no sign that new data was loading, + and the histogram could briefly swap its chart for "Loading Chart Data...". + Both now keep their previous data on screen and pulse while the refetch runs, + like the other charts. + +- 0d2425d5: feat: Allow configuring dashboard filters as single-select +- 1ce8b88e: fix: rank Map keys by frequency when a text index serves key discovery + + The two `mergeTreeTextIndex` paths in `getMapKeys` grouped keys and applied + `LIMIT maxKeys` with no `ORDER BY`, so on a column with more keys than the + limit the filter sidebar showed an arbitrary subset. They now order by + `sum(cardinality) DESC, key`, which keeps the most frequent keys, as the key + rollup path already does with `sum(count) DESC`. + +- 4477f304: feat: show a trace's total wall-clock duration in the waterfall controls bar +- 01fdc5d4: ui: Extract FilterPill, add filter editor components +- Updated dependencies [14003f08] +- Updated dependencies [76d33d73] +- Updated dependencies [07c93656] +- Updated dependencies [6873416d] +- Updated dependencies [0b855534] +- Updated dependencies [c2e21cf5] +- Updated dependencies [cf5b831f] +- Updated dependencies [7aeb6215] +- Updated dependencies [0846f3b2] +- Updated dependencies [e61461be] +- Updated dependencies [6ea5f52c] +- Updated dependencies [ff5befa8] +- Updated dependencies [d8b1cdfa] +- Updated dependencies [1be9de8f] +- Updated dependencies [837c6837] +- Updated dependencies [ab703243] +- Updated dependencies [0d2425d5] +- Updated dependencies [68082b67] +- Updated dependencies [1ce8b88e] +- Updated dependencies [e88cf3d5] + - @hyperdx/api@2.41.0 + - @hyperdx/common-utils@0.31.0 + ## 2.40.0 ### Minor Changes diff --git a/packages/app/package.json b/packages/app/package.json index ffcb1e8453..eab6050462 100644 --- a/packages/app/package.json +++ b/packages/app/package.json @@ -1,6 +1,6 @@ { "name": "@hyperdx/app", - "version": "2.40.0", + "version": "2.41.0", "private": true, "license": "MIT", "engines": { @@ -39,7 +39,7 @@ "@hookform/resolvers": "^3.9.0", "@hyperdx/api": "workspace:*", "@hyperdx/browser": "^0.22.1", - "@hyperdx/common-utils": "^0.30.0", + "@hyperdx/common-utils": "^0.31.0", "@hyperdx/node-opentelemetry": "^0.9.0", "@mantine/core": "^9.0.0", "@mantine/dates": "^9.0.0", diff --git a/packages/cli/CHANGELOG.md b/packages/cli/CHANGELOG.md index a40cdad27f..b7b05c0636 100644 --- a/packages/cli/CHANGELOG.md +++ b/packages/cli/CHANGELOG.md @@ -1,5 +1,11 @@ # @hyperdx/cli +## 0.7.0 + +### Minor Changes + +- 68082b67: feat: add stacked line (stacked area) time-series display type + ## 0.6.4 ### Patch Changes diff --git a/packages/cli/package.json b/packages/cli/package.json index dd4eb114e5..0db54f9063 100644 --- a/packages/cli/package.json +++ b/packages/cli/package.json @@ -1,6 +1,6 @@ { "name": "@hyperdx/cli", - "version": "0.6.4", + "version": "0.7.0", "license": "MIT", "type": "module", "repository": { @@ -41,7 +41,7 @@ }, "devDependencies": { "@clickhouse/client": "1.23.0-head.fae5998.1", - "@hyperdx/common-utils": "^0.30.0", + "@hyperdx/common-utils": "^0.31.0", "@jest/globals": "^30.2.0", "@types/crypto-js": "^4.2.2", "@types/jest": "^29.5.14", diff --git a/packages/common-utils/CHANGELOG.md b/packages/common-utils/CHANGELOG.md index 1dc4b981cf..7558f15659 100644 --- a/packages/common-utils/CHANGELOG.md +++ b/packages/common-utils/CHANGELOG.md @@ -1,5 +1,82 @@ # @hyperdx/common-utils +## 0.31.0 + +### Minor Changes + +- 6873416d: feat: Add a series mode to builder heatmaps +- ff5befa8: Support "Minimum auto granularity" on PromQL sources. It floors the step of charts on auto granularity, as it does for metric sources, and `$__rate_interval` now uses it as the source's scrape interval (still 15s when unset) instead of always assuming 15s. A granularity picked on a tile is never changed. +- d8b1cdfa: feat: Attribute PromQL queries to the dashboard, tile or search that issued them, through both the `prometheusQuery`/`prometheusQueryRange` table functions and ClickHouse's Prometheus HTTP API +- ab703243: feat: attribute ClickHouse queries to the dashboard, tile, search or alert that + issued them + + A row in `system.query_log` previously couldn't be attributed to the part of + HyperDX that produced it. Now every query HyperDX runs has a small JSON + `log_comment`, plus a `query_id` starting with `hdx-`. + + Attribute load after the fact: + + ```sql + SELECT + JSONExtractString(log_comment, 'surface') AS surface, + JSONExtractString(log_comment, 'dashboard') AS dashboard, + JSONExtractString(log_comment, 'tile') AS tile, + count(), + sum(read_rows) + FROM system.query_log + WHERE type = 'QueryFinish' AND log_comment != '' AND query_id like 'hdx-%' + GROUP BY ALL + ORDER BY sum(read_rows) DESC + ``` + + Or spot a query while it is still running, in `system.processes`, where the + `query_id` names the surface with no JSON parsing needed. + + The payload records which part of the product asked (a dashboard, a search, an + alert, an MCP tool, the chart explorer, session replay, field lookups, and so + on), the dashboard and tile or saved search id, the source id, and on the server + the trace id of the request. Field lookups and autocomplete are labelled too, so + they can be told apart from a user's chart queries. + + The exception is queries that skip settings processing: the `system.settings`, + server version and Cloud-detection probes, and the onboarding connection check. + They get a `query_id` but an empty `log_comment`. + +- 68082b67: feat: add stacked line (stacked area) time-series display type + +### Patch Changes + +- 07c93656: fix: cast FixedString columns before implicit hasToken search + + A bare search term against a FixedString column such as OTel TraceId compiled to + hasToken(lower(TraceId), ...), which ClickHouse rejects. Those haystacks are now + CAST to String first. + +- 0b855534: fix: fall back to the Map key scan when the text index read fails + + `getMapKeys` returned an empty list whenever its `mergeTreeTextIndex` query + failed, so the rollup and bounded `mapKeys` scan paths never ran. ClickHouse + refuses `mergeTreeTextIndex` with `ACCESS_DENIED` on any table with a row + policy, which left search autocomplete with no Map keys on those tables. A + failed text index read now falls through to the next strategy. After a row + policy denial it skips the key rollup table, which the policy doesn't cover, + and reads keys only from the policy-filtered source table. + +- 0846f3b2: Include the requested Map-key limit in metadata cache keys so MCP discovery and AI field discovery cannot reuse each other's differently limited results. +- e61461be: feat: auto-detect a PromQL source during onboarding + + When PromQL is enabled (`NEXT_PUBLIC_ENABLE_PROMQL=true`), onboarding source auto-detection now also creates a PromQL source for a ClickHouse TimeSeries engine table. It prefers `prometheus.metrics` (the table the ClickHouse Prometheus docs suggest), then a table named `metrics_ts`, and otherwise picks the only TimeSeries table on the connection. A service with only a TimeSeries table is no longer sent to manual source setup. + +- 1be9de8f: feat: Add a promql variable format that escapes based on single/multi-select +- 0d2425d5: feat: Allow configuring dashboard filters as single-select +- 1ce8b88e: fix: rank Map keys by frequency when a text index serves key discovery + + The two `mergeTreeTextIndex` paths in `getMapKeys` grouped keys and applied + `LIMIT maxKeys` with no `ORDER BY`, so on a column with more keys than the + limit the filter sidebar showed an arbitrary subset. They now order by + `sum(cardinality) DESC, key`, which keeps the most frequent keys, as the key + rollup path already does with `sum(count) DESC`. + ## 0.30.0 ### Minor Changes diff --git a/packages/common-utils/package.json b/packages/common-utils/package.json index 9f5b58399e..696473adb6 100644 --- a/packages/common-utils/package.json +++ b/packages/common-utils/package.json @@ -1,7 +1,7 @@ { "name": "@hyperdx/common-utils", "description": "Common utilities for HyperDX application", - "version": "0.30.0", + "version": "0.31.0", "license": "MIT", "private": true, "files": [ diff --git a/packages/otel-collector/CHANGELOG.md b/packages/otel-collector/CHANGELOG.md index d241c974d2..19379624e1 100644 --- a/packages/otel-collector/CHANGELOG.md +++ b/packages/otel-collector/CHANGELOG.md @@ -1,5 +1,7 @@ # @hyperdx/otel-collector +## 2.41.0 + ## 2.40.0 ### Minor Changes diff --git a/packages/otel-collector/package.json b/packages/otel-collector/package.json index 8561ec1bcf..f132cbbe1d 100644 --- a/packages/otel-collector/package.json +++ b/packages/otel-collector/package.json @@ -1,7 +1,7 @@ { "name": "@hyperdx/otel-collector", "description": "HyperDX OpenTelemetry Collector configuration and Docker image", - "version": "2.40.0", + "version": "2.41.0", "license": "MIT", "private": true } diff --git a/yarn.lock b/yarn.lock index b3c1157b52..7daa71f771 100644 --- a/yarn.lock +++ b/yarn.lock @@ -4721,7 +4721,7 @@ __metadata: "@braintree/sanitize-url": "npm:^7.1.1" "@clickhouse/client-common": "npm:1.23.0-head.fae5998.1" "@esm2cjs/p-queue": "npm:^7.3.0" - "@hyperdx/common-utils": "npm:^0.30.0" + "@hyperdx/common-utils": "npm:^0.31.0" "@hyperdx/node-opentelemetry": "npm:^0.9.0" "@hyperdx/passport-local-mongoose": "npm:^9.0.1" "@modelcontextprotocol/sdk": "npm:^1.27.1" @@ -4815,7 +4815,7 @@ __metadata: "@hookform/resolvers": "npm:^3.9.0" "@hyperdx/api": "workspace:*" "@hyperdx/browser": "npm:^0.22.1" - "@hyperdx/common-utils": "npm:^0.30.0" + "@hyperdx/common-utils": "npm:^0.31.0" "@hyperdx/node-opentelemetry": "npm:^0.9.0" "@mantine/core": "npm:^9.0.0" "@mantine/dates": "npm:^9.0.0" @@ -4942,7 +4942,7 @@ __metadata: resolution: "@hyperdx/cli@workspace:packages/cli" dependencies: "@clickhouse/client": "npm:1.23.0-head.fae5998.1" - "@hyperdx/common-utils": "npm:^0.30.0" + "@hyperdx/common-utils": "npm:^0.31.0" "@jest/globals": "npm:^30.2.0" "@types/crypto-js": "npm:^4.2.2" "@types/jest": "npm:^29.5.14" @@ -4969,7 +4969,7 @@ __metadata: languageName: unknown linkType: soft -"@hyperdx/common-utils@npm:^0.30.0, @hyperdx/common-utils@workspace:packages/common-utils": +"@hyperdx/common-utils@npm:^0.31.0, @hyperdx/common-utils@workspace:packages/common-utils": version: 0.0.0-use.local resolution: "@hyperdx/common-utils@workspace:packages/common-utils" dependencies: