937e043a1c
Some checks failed
Main / unit (push) Has been cancelled
Knip - Unused Code Analysis / knip (push) Has been cancelled
Main / lint (push) Has been cancelled
Main / integration (push) Has been cancelled
Main / otel-unit-test (push) Has been cancelled
Main / otel-smoke-test (push) Has been cancelled
Main / e2e-tests (push) Has been cancelled
Main / ClickHouse Bundle Build (push) Has been cancelled
Push Downstream / push-downstream (push) Has been cancelled
Release / Check Changesets (push) Has been cancelled
Main / End-to-End Tests (push) Has been cancelled
Release / Build App (amd64) (push) Has been cancelled
Release / Build OTel Collector (amd64) (push) Has been cancelled
Release / Check if version exists (push) Has been cancelled
Release / Build OTel Collector (arm64) (push) Has been cancelled
Release / Publish OTel Collector Manifest (push) Has been cancelled
Release / Build App (arm64) (push) Has been cancelled
Release / Publish App Manifest (push) Has been cancelled
Release / Build Local (amd64) (push) Has been cancelled
Release / Build Local (arm64) (push) Has been cancelled
Release / Publish Local Manifest (push) Has been cancelled
Release / Build All-in-One (amd64) (push) Has been cancelled
Release / Build All-in-One (arm64) (push) Has been cancelled
Release / Publish All-in-One Manifest (push) Has been cancelled
Release / Release CLI Binaries (push) Has been cancelled
Release / Notify Helm-Charts Downstream (push) Has been cancelled
Release / Notify CH Downstream (push) Has been cancelled
Release / notify_clickhouse_clickstack (push) Has been cancelled
Release / slack-notify-failure (push) Has been cancelled
Release / OpenTelemetry Export Trace (push) Has been cancelled
## Summary
The filter sidebar rendered two separate accordion items for the same map sub-field (e.g. two `time (1)` rows under `LogAttributes`, both showing the same value) whenever a Lucene URL round-trip put a map filter back into `filterState`. Root cause: `filterState` stores map sub-keys in dot notation (`LogAttributes.time`) after `setFilterValue`'s `parseKeyPath().join('.')` normalization, while the facet query returns the same logical key in bracket notation (`LogAttributes['time']`); the merge in `shownFacets` treated them as distinct.
`groupFacetsByBaseName` now collapses children by `(baseName, propertyPath)` and keeps the bracket form so `child.key` stays valid for "Load more" SQL. A new `getFilterStateEntry` helper tolerates either form when reading `filterState`, so the user's selection still resolves on the merged child. Writes are unchanged.
### Screenshots or video
| Before | After |
| :----- | :---- |
| Two `time` rows under `LogAttributes`, only the first checked. | Single `time` row with the selection preserved. |
### How to test on Vercel preview
**Preview routes:** /search
**Steps:**
1. Open the Search page on a source whose `LogAttributes` (or any Map column) has at least one observed key — `service.name` is a good candidate on the demo data.
2. Append `&where=LogAttributes.service.name%3A%22api%22` (substitute any real attribute key/value) to the URL and reload.
3. Expand `LogAttributes` in the filter sidebar.
4. Verify only one row appears for the filtered key (no duplicate accordion item), the checkbox shows the selection, and clicking "Load more" surfaces additional values.
### References
- Linear Issue: [HDX-4340](https://linear.app/clickhouse/issue/HDX-4340/filtering-on-map-keyvals-results-in-duplicate-map-entries-in-the)
- Related PRs:
|
||
|---|---|---|
| .changeset | ||
| .claude | ||
| .config | ||
| .cursor | ||
| .github | ||
| .husky | ||
| .opencode/commands | ||
| .vex | ||
| .vscode | ||
| .yarn/releases | ||
| agent_docs | ||
| docker | ||
| docs/assets | ||
| packages | ||
| proxy | ||
| scripts | ||
| smoke-tests/otel-collector | ||
| .env | ||
| .gitattributes | ||
| .gitignore | ||
| .kodiak.toml | ||
| .mcp.json | ||
| .nvmrc | ||
| .prettierignore | ||
| .prettierrc | ||
| .yarnrc.yml | ||
| AGENTS.md | ||
| CLAUDE.md | ||
| CONTRIBUTING.md | ||
| DEPLOY.md | ||
| docker-compose.ci.yml | ||
| docker-compose.dev.yml | ||
| docker-compose.yml | ||
| knip.json | ||
| LICENSE | ||
| LOCAL.md | ||
| Makefile | ||
| MCP.md | ||
| nx.json | ||
| package.json | ||
| README.md | ||
| tsconfig.base.json | ||
| vercel.json | ||
| version.sh | ||
| yarn.lock | ||
HyperDX
HyperDX, a core component of ClickStack, helps engineers quickly figure out why production is broken by making it easy to search & visualize logs and traces on top of any ClickHouse cluster (imagine Kibana, for ClickHouse).
Documentation • Chat on Discord • Live Demo • Bug Reports • Contributing • Website
- 🕵️ Correlate/search logs, metrics, session replays and traces all in one place
- 📝 Schema agnostic, works on top of your existing ClickHouse schema
- 🔥 Blazing fast searches & visualizations optimized for ClickHouse
- 🔍 Intuitive full-text search and property search syntax (ex.
level:err), SQL optional! - 📊 Analyze trends in anomalies with event deltas
- 🔔 Set up alerts in just a few clicks
- 📈 Dashboard high cardinality events without a complex query language
{Native JSON string querying- ⚡ Live tail logs and traces to always get the freshest events
- 🔭 OpenTelemetry supported out of the box
- ⏱️ Monitor health and performance from HTTP requests to DB queries (APM)
Spinning Up HyperDX
HyperDX can be deployed as part of ClickStack, which includes ClickHouse, HyperDX, OpenTelemetry Collector and MongoDB.
docker run -p 8080:8080 -p 4317:4317 -p 4318:4318 docker.hyperdx.io/hyperdx/hyperdx-all-in-one
Afterwards, you can visit http://localhost:8080 to access the HyperDX UI.
If you already have an existing ClickHouse instance, want to use a single container locally, or are looking for production deployment instructions, you can view the different deployment options in our deployment docs.
If your server is behind a firewall, you'll need to open/forward port 8080, 8000 and 4318 on your firewall for the UI, API and OTel collector respectively.
We recommend at least 4GB of RAM and 2 cores for testing.
Hosted ClickHouse Cloud
You can also deploy HyperDX with ClickHouse Cloud, you can sign up for free and get started in just minutes.
Instrumenting Your App
To get logs, metrics, traces, session replay, etc into HyperDX, you'll need to instrument your app to collect and send telemetry data over to your HyperDX instance.
We provide a set of SDKs and integration options to make it easier to get started with HyperDX, such as Browser, Node.js, and Python
You can find the full list in our docs.
OpenTelemetry
Additionally, HyperDX is compatible with OpenTelemetry, a vendor-neutral standard for instrumenting your application backed by CNCF. Supported languages/platforms include:
- Kubernetes
- Javascript
- Python
- Java
- Go
- Ruby
- PHP
- .NET
- Elixir
- Rust
(Full list here)
Once HyperDX is running, you can point your OpenTelemetry SDK to the
OpenTelemetry collector spun up at http://localhost:4318.
Contributing
We welcome all contributions! There's many ways to contribute to the project, including but not limited to:
- Opening a PR (Contribution Guide)
- Submitting feature requests or bugs
- Improving our product or contribution documentation
- Voting on open issues or contributing use cases to a feature request
Motivation
Our mission is to help engineers ship reliable software. To enable that, we believe every engineer needs to be able to easily leverage production telemetry to quickly solve burning production issues.
However, in our experience, the existing tools we've used tend to fall short in a few ways:
- They're expensive, and the pricing has failed to scale with TBs of telemetry becoming the norm, leading to teams aggressively cutting the amount of data they can collect.
- They're hard to use, requiring full-time SREs to set up, and domain experts to use confidently.
- They requiring hopping from tool to tool (logs, session replay, APM, exceptions, etc.) to stitch together the clues yourself.
We hope you give HyperDX in ClickStack a try and let us know how we're doing!
Contact
HyperDX Usage Data
HyperDX collects anonymized usage data for open source deployments. This data
supports our mission for observability to be available to any team and helps
support our open source product run in a variety of different environments.
While we hope you will continue to support our mission in this way, you may opt
out of usage data collection by setting the USAGE_STATS_ENABLED environment
variable to false. Thank you for supporting the development of HyperDX!