Release HyperDX

[github-actions]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@hyperdx/cli@0.4.2

Patch Changes

• b20275c: fix(cli): exit with non-zero code when upload-sourcemaps fails

  The upload-sourcemaps command now exits with code 1 when uploads fail
  (missing source maps, pre-signed URL request failure, authentication failure,
  or any per-file upload failure after retries). Previously these failures were
  logged to stderr but the process exited cleanly with code 0, causing CI
  pipelines to treat failed uploads as successes.

• 19cd7c9: fix: only use pk and row uniqueness to look up a row

• 8810ff0: feat: Add option for force-enabling/disabling text index support

@hyperdx/app@2.28.0

Minor Changes

• 1df7583: feat: emit Lucene conditions from sidebar/dashboard filters to enable KV items direct_read optimization on Map columns

  Legacy type: 'sql' filters in URLs are automatically migrated to Lucene
  on page load. The persisted DashboardFilter.expression in MongoDB is unchanged.

Patch Changes

• 937e043: fix: collapse duplicate map sub-key entries in the search filter sidebar (HDX-4340)

  A map sub-field stored in filterState under dot notation (e.g. LogAttributes.time,
  from a Lucene URL round-trip) and the same key returned by the facet query under
  bracket notation (e.g. LogAttributes['time']) no longer render as two separate
  accordion items. The merged entry keeps the bracket form so "Load more" stays
  valid, and the user's selection still resolves via a tolerant filterState lookup.

• dcab1cb: feat: default the direct_read map column optimization on supported ClickHouse versions

  The full-text-search logs schema (00002_otel_logs.sql) now ships with
  ResourceAttributeItems, ScopeAttributeItems, and LogAttributeItems
  ALIAS columns plus their text(tokenizer='array') skip indexes. The
  traces schema (00005_otel_traces.sql) similarly gains
  ResourceAttributeItems and SpanAttributeItems ALIAS columns with
  matching items indexes. New installs and freshly migrated tables get
  the optimization automatically — no manual ALTER TABLE required.

  Note: the traces table previously used only bloom_filter skip indexes
  and worked on any ClickHouse version. The added text(tokenizer='array')
  items indexes raise the minimum ClickHouse version required to create
  the traces table to >= 26.2. Existing tables on older clusters are
  unaffected (CREATE TABLE IF NOT EXISTS is a no-op).

  At query time, the app gates the Map['key'] = 'value' →
  has(<MapItems>, concat('key', '=', 'value')) rewrite on the connected
  ClickHouse server version (SELECT version(), cached per connection).
  The gate only applies to ALIAS items columns, which are computed at
  query time and therefore depend on the server being able to perform a
  direct_read against the underlying Map's tuple storage. The direct_read
  feature was backported into multiple stable 26.x release lines, so the
  gate uses a per-branch minimum:

  • 26.2 line: >= 26.2.19.43
  • 26.3 line: >= 26.3.12.3
  • 26.4 line: >= 26.4.3.37
  • 26.5+ : always supported

  ALIAS items columns on servers below their branch's threshold continue
  to compile filters into the original Map-subscript form.

  MATERIALIZED items columns are always used when available, regardless
  of ClickHouse version. MATERIALIZED columns are physically stored on
  disk, so has(items, ...) reads them directly and works on any
  ClickHouse version that supports the text index itself. Operators who
  want the optimization on servers below the backport cutoffs can
  ALTER TABLE to materialize the items columns.

• 923b544: feat: preserve compatible filters when switching sources

• b94b8ef: fix: persist column widths in search results table

• 19cd7c9: fix: only use pk and row uniqueness to look up a row

• 633eda6: refactor: Use new VirtualMultiSelect for dashboard filter inputs

• 8938b05: fix: let "Load more" surface unselected values in exact filter mode

• 04a5a92: feat: Add source scoping to dashboard filters

• 8810ff0: feat: Add option for force-enabling/disabling text index support

• a8eb27d: feat: filters reflect all values, not search aware; filters use metadata MVs if available

• Updated dependencies [d134212]

• Updated dependencies [dcab1cb]

• Updated dependencies [a945fa0]

• Updated dependencies [1df7583]

• Updated dependencies [b30dfe0]

• Updated dependencies [dcb8582]

• Updated dependencies [c3a8aa5]

• Updated dependencies [07911fd]

• Updated dependencies [04a5a92]

• Updated dependencies [8810ff0]

• Updated dependencies [a8eb27d]

  • @hyperdx/api@2.28.0
  • @hyperdx/common-utils@0.20.0

@hyperdx/common-utils@0.20.0

Minor Changes

• dcab1cb: feat: default the direct_read map column optimization on supported ClickHouse versions

  The full-text-search logs schema (00002_otel_logs.sql) now ships with
  ResourceAttributeItems, ScopeAttributeItems, and LogAttributeItems
  ALIAS columns plus their text(tokenizer='array') skip indexes. The
  traces schema (00005_otel_traces.sql) similarly gains
  ResourceAttributeItems and SpanAttributeItems ALIAS columns with
  matching items indexes. New installs and freshly migrated tables get
  the optimization automatically — no manual ALTER TABLE required.

  Note: the traces table previously used only bloom_filter skip indexes
  and worked on any ClickHouse version. The added text(tokenizer='array')
  items indexes raise the minimum ClickHouse version required to create
  the traces table to >= 26.2. Existing tables on older clusters are
  unaffected (CREATE TABLE IF NOT EXISTS is a no-op).

  At query time, the app gates the Map['key'] = 'value' →
  has(<MapItems>, concat('key', '=', 'value')) rewrite on the connected
  ClickHouse server version (SELECT version(), cached per connection).
  The gate only applies to ALIAS items columns, which are computed at
  query time and therefore depend on the server being able to perform a
  direct_read against the underlying Map's tuple storage. The direct_read
  feature was backported into multiple stable 26.x release lines, so the
  gate uses a per-branch minimum:

  • 26.2 line: >= 26.2.19.43
  • 26.3 line: >= 26.3.12.3
  • 26.4 line: >= 26.4.3.37
  • 26.5+ : always supported

  ALIAS items columns on servers below their branch's threshold continue
  to compile filters into the original Map-subscript form.

  MATERIALIZED items columns are always used when available, regardless
  of ClickHouse version. MATERIALIZED columns are physically stored on
  disk, so has(items, ...) reads them directly and works on any
  ClickHouse version that supports the text index itself. Operators who
  want the optimization on servers below the backport cutoffs can
  ALTER TABLE to materialize the items columns.

• 1df7583: feat: emit Lucene conditions from sidebar/dashboard filters to enable KV items direct_read optimization on Map columns

  Legacy type: 'sql' filters in URLs are automatically migrated to Lucene
  on page load. The persisted DashboardFilter.expression in MongoDB is unchanged.

Patch Changes

• a945fa0: feat(mcp): add hyperdx_event_deltas tool

  Add hyperdx_event_deltas MCP tool that compares two row groups (target
  vs baseline) and ranks properties by how much their value distributions
  differ. Same algorithm as the in-app Event Deltas view.

  Extract shared event-deltas algorithm from the UI into
  @hyperdx/common-utils/src/core/eventDeltas.ts so it can be used by
  both the frontend and the MCP server.

• b30dfe0: fix: support text index on lower(Body) with no preprocessor

• dcb8582: fix: escape colons in Lucene field names so filters on Map sub-keys containing
  : (e.g. LogAttributes['foo:bar']) parse correctly

  filtersToQuery now backslash-escapes : and \ in the emitted Lucene field
  name, and parseLuceneFilter + the SQL serializer decode those placeholders
  when consuming the AST so the original key is restored end-to-end.

• 04a5a92: feat: Add source scoping to dashboard filters

• 8810ff0: feat: Add option for force-enabling/disabling text index support

• a8eb27d: feat: filters reflect all values, not search aware; filters use metadata MVs if available

@hyperdx/api@2.28.0

Patch Changes

• d134212: feat(mcp): add hyperdx_describe_source tool and slim list_sources to catalog

  Add hyperdx_describe_source — returns full column schema, map attribute
  keys, and sampled low-cardinality values (SeverityText, StatusCode,
  ServiceName, etc.) for a single source. Uses existing rollup tables for
  performant value sampling.

  Slim hyperdx_list_sources to a lightweight MongoDB-only catalog (no
  ClickHouse queries). Source tools moved to a dedicated tools/sources/
  module.

  All query tool descriptions and prompts updated to reference the two-step
  list_sources → describe_source discovery workflow.

• a945fa0: feat(mcp): add hyperdx_event_deltas tool

  Add hyperdx_event_deltas MCP tool that compares two row groups (target
  vs baseline) and ranks properties by how much their value distributions
  differ. Same algorithm as the in-app Event Deltas view.

  Extract shared event-deltas algorithm from the UI into
  @hyperdx/common-utils/src/core/eventDeltas.ts so it can be used by
  both the frontend and the MCP server.

• c3a8aa5: feat(mcp): rewrite dashboard authoring prompts and expose filters on hyperdx_save_dashboard

  The create_dashboard prompt now leads with a design checklist (alias every select item including number tiles, schema gap on groupBy so tables don't render arrayElement(SpanAttributes, '...') as the column header, RED columns with aliases, per-series numberFormat for durations, groupByColumnsOnLeft for inventory tables, dashboard-level filters instead of per-tile where literals, one-metric-per-tile for metric sources, required containers at five or more tiles, post-save validation of every tile, no title-recap markdown). The wall-of-JSON canonical example is gone; the dashboard_examples patterns carry the concrete shapes.

  The dashboard_examples set is replaced with four verified patterns (service_inventory, service_detail, log_analytics, backend_dependencies) plus the existing infrastructure_sql. Each non-SQL example leads with a "When to use" header and a "Why this shape" note so the model picks by intent, not by surface keyword match. Examples were built and rendered on a live dev stack before landing.

  The query_guide prompt gains a DASHBOARD FILTERS section that documents the filters: [{ type, name, expression, sourceId, where?, whereLanguage? }] shape, a NUMBER FORMAT section that explains the per-series vs. chart-level distinction, and a PER-TILE TYPE CONSTRAINTS note that metric tiles take exactly one select item per tile.

  hyperdx_save_dashboard now accepts filters on its input schema, reusing externalDashboardFilterSchemaWithId so the MCP and REST surfaces stay in lockstep and the existing convertExternalFiltersToInternal helper handles the conversion without translation. Filters round-trip through create, get, and update.

  Voice pass: every prompt string is now em-dash-free.

• 07911fd: feat(mcp): add trace waterfall and breakdown tools

  Add hyperdx_trace_waterfall — fetch all spans in a single trace as a
  parent/child waterfall tree with optional correlated logs. Supports
  auto-pick by slowest, first error, or most recent trace.

  Add hyperdx_trace_top_time_consuming_operations — aggregate breakdown
  of child operations consuming the most cumulative time across traces
  matching a parent-span filter. Same algorithm as the in-app "Top Most
  Time Consuming Operations" chart.

• 04a5a92: feat: Add source scoping to dashboard filters

• 8810ff0: feat: Add option for force-enabling/disabling text index support

• a8eb27d: feat: filters reflect all values, not search aware; filters use metadata MVs if available

• Updated dependencies [dcab1cb]

• Updated dependencies [a945fa0]

• Updated dependencies [1df7583]

• Updated dependencies [b30dfe0]

• Updated dependencies [dcb8582]

• Updated dependencies [04a5a92]

• Updated dependencies [8810ff0]

• Updated dependencies [a8eb27d]

  • @hyperdx/common-utils@0.20.0

@hyperdx/otel-collector@2.28.0

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
hyperdx-oss	Ready	Preview, Comment	May 27, 2026 8:12am