[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-9881":3},{"id":4,"name":5,"fullName":6,"owner":7,"repo":5,"description":8,"homepage":9,"htmlUrl":10,"language":11,"languages":10,"totalLinesOfCode":10,"stars":12,"forks":13,"watchers":14,"openIssues":15,"contributorsCount":16,"subscribersCount":16,"size":16,"stars1d":17,"stars7d":18,"stars30d":19,"stars90d":16,"forks30d":16,"starsTrendScore":20,"compositeScore":21,"rankGlobal":10,"rankLanguage":10,"license":22,"archived":23,"fork":23,"defaultBranch":24,"hasWiki":25,"hasPages":23,"topics":26,"createdAt":10,"pushedAt":10,"updatedAt":46,"readmeContent":47,"aiSummary":48,"trendingCount":16,"starSnapshotCount":16,"syncStatus":49,"lastSyncTime":50,"discoverSource":51},9881,"hyperdx","hyperdxio\u002Fhyperdx","hyperdxio","Resolve production issues, fast. An open source observability platform unifying session replays, logs, metrics, traces and errors powered by ClickHouse and OpenTelemetry.","https:\u002F\u002Fhyperdx.io\u002F",null,"TypeScript",9588,409,28,100,0,5,16,90,18,38.84,"MIT License",false,"main",true,[27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45],"alerting","analytics","apm","application-monitoring","clickhouse","dashboard","frontend-monitoring","kubernetes","log-management","logs","metrics","monitoring","observability","opentelemetry","react","self-hosted","session-replay","traces","typescript","2026-06-12 02:02:13","\u003Cp align=\"center\">\n  \u003Ca href=\"https:\u002F\u002Fhyperdx.io\">\n    \u003Cpicture>\n      \u003Csource media=\"(prefers-color-scheme: dark)\" srcset=\".\u002F.github\u002Fimages\u002Flogo_dark.png#gh-dark-mode-only\">\n      \u003Cimg alt=\"hyperdx logo\" src=\".\u002F.github\u002Fimages\u002Flogo_light.png#gh-light-mode-only\">\n    \u003C\u002Fpicture>\n  \u003C\u002Fa>\n\u003C\u002Fp>\n\n---\n\n# HyperDX\n\n[HyperDX](https:\u002F\u002Fhyperdx.io), a core component of\n[ClickStack](https:\u002F\u002Fclickhouse.com\u002Fuse-cases\u002Fobservability), helps engineers\nquickly figure out why production is broken by making it easy to search &\nvisualize logs and traces on top of any ClickHouse cluster (imagine Kibana, for\nClickHouse).\n\n\u003Cp align=\"center\">\n  \u003Ca href=\"https:\u002F\u002Fclickhouse.com\u002Fdocs\u002Fuse-cases\u002Fobservability\u002Fclickstack\u002Foverview\">Documentation\u003C\u002Fa> • \u003Ca href=\"https:\u002F\u002Fhyperdx.io\u002Fdiscord\">Chat on Discord\u003C\u002Fa>  • \u003Ca href=\"https:\u002F\u002Fplay.hyperdx.io\u002Fsearch\">Live Demo\u003C\u002Fa>  • \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fhyperdxio\u002Fhyperdx\u002Fissues\u002Fnew\">Bug Reports\u003C\u002Fa> • \u003Ca href=\".\u002FCONTRIBUTING.md\">Contributing\u003C\u002Fa> • \u003Ca href=\"https:\u002F\u002Fclickhouse.com\u002Fuse-cases\u002Fobservability\">Website\u003C\u002Fa>\n\u003C\u002Fp>\n\n- 🕵️ Correlate\u002Fsearch logs, metrics, session replays and traces all in one place\n- 📝 Schema agnostic, works on top of your existing ClickHouse schema\n- 🔥 Blazing fast searches & visualizations optimized for ClickHouse\n- 🔍 Intuitive full-text search and property search syntax (ex. `level:err`),\n  SQL optional!\n- 📊 Analyze trends in anomalies with event deltas\n- 🔔 Set up alerts in just a few clicks\n- 📈 Dashboard high cardinality events without a complex query language\n- `{` Native JSON string querying\n- ⚡ Live tail logs and traces to always get the freshest events\n- 🔭 OpenTelemetry supported out of the box\n- ⏱️ Monitor health and performance from HTTP requests to DB queries (APM)\n\n\u003Cbr\u002F>\n\u003Cimg alt=\"Search logs and traces all in one place\" src=\".\u002F.github\u002Fimages\u002Fsearch_splash.png\" title=\"Search logs and traces all in one place\">\n\n## Spinning Up HyperDX\n\nHyperDX can be deployed as part of ClickStack, which includes ClickHouse,\nHyperDX, OpenTelemetry Collector and MongoDB.\n\n```bash\ndocker run -p 8080:8080 -p 4317:4317 -p 4318:4318 docker.hyperdx.io\u002Fhyperdx\u002Fhyperdx-all-in-one\n```\n\nAfterwards, you can visit http:\u002F\u002Flocalhost:8080 to access the HyperDX UI.\n\nIf you already have an existing ClickHouse instance, want to use a single\ncontainer locally, or are looking for production deployment instructions, you\ncan view the different deployment options in our\n[deployment docs](https:\u002F\u002Fclickhouse.com\u002Fdocs\u002Fuse-cases\u002Fobservability\u002Fclickstack\u002Fdeployment).\n\n> If your server is behind a firewall, you'll need to open\u002Fforward port 8080,\n> 8000 and 4318 on your firewall for the UI, API and OTel collector\n> respectively.\n\n> We recommend at least 4GB of RAM and 2 cores for testing.\n\n### Hosted ClickHouse Cloud\n\nYou can also deploy HyperDX with ClickHouse Cloud, you can\n[sign up for free](https:\u002F\u002Fconsole.clickhouse.cloud\u002FsignUp) and get started in\njust minutes.\n\n## Instrumenting Your App\n\nTo get logs, metrics, traces, session replay, etc into HyperDX, you'll need to\ninstrument your app to collect and send telemetry data over to your HyperDX\ninstance.\n\nWe provide a set of SDKs and integration options to make it easier to get\nstarted with HyperDX, such as\n[Browser](https:\u002F\u002Fclickhouse.com\u002Fdocs\u002Fuse-cases\u002Fobservability\u002Fclickstack\u002Fsdks\u002Fbrowser),\n[Node.js](https:\u002F\u002Fclickhouse.com\u002Fdocs\u002Fuse-cases\u002Fobservability\u002Fclickstack\u002Fsdks\u002Fnodejs),\nand\n[Python](https:\u002F\u002Fclickhouse.com\u002Fdocs\u002Fuse-cases\u002Fobservability\u002Fclickstack\u002Fsdks\u002Fpython)\n\nYou can find the full list in\n[our docs](https:\u002F\u002Fclickhouse.com\u002Fdocs\u002Fuse-cases\u002Fobservability\u002Fclickstack).\n\n**OpenTelemetry**\n\nAdditionally, HyperDX is compatible with\n[OpenTelemetry](https:\u002F\u002Fopentelemetry.io\u002F), a vendor-neutral standard for\ninstrumenting your application backed by CNCF. Supported languages\u002Fplatforms\ninclude:\n\n- Kubernetes\n- Javascript\n- Python\n- Java\n- Go\n- Ruby\n- PHP\n- .NET\n- Elixir\n- Rust\n\n(Full list [here](https:\u002F\u002Fopentelemetry.io\u002Fdocs\u002Finstrumentation\u002F))\n\nOnce HyperDX is running, you can point your OpenTelemetry SDK to the\nOpenTelemetry collector spun up at `http:\u002F\u002Flocalhost:4318`.\n\n## Contributing\n\nWe welcome all contributions! There's many ways to contribute to the project,\nincluding but not limited to:\n\n- Opening a PR ([Contribution Guide](.\u002FCONTRIBUTING.md))\n- [Submitting feature requests or bugs](https:\u002F\u002Fgithub.com\u002Fhyperdxio\u002Fhyperdx\u002Fissues\u002Fnew)\n- Improving our product or contribution documentation\n- Voting on [open issues](https:\u002F\u002Fgithub.com\u002Fhyperdxio\u002Fhyperdx\u002Fissues) or\n  contributing use cases to a feature request\n\n## Motivation\n\nOur mission is to help engineers ship reliable software. To enable that, we\nbelieve every engineer needs to be able to easily leverage production telemetry\nto quickly solve burning production issues.\n\nHowever, in our experience, the existing tools we've used tend to fall short in\na few ways:\n\n1. They're expensive, and the pricing has failed to scale with TBs of telemetry\n   becoming the norm, leading to teams aggressively cutting the amount of data\n   they can collect.\n2. They're hard to use, requiring full-time SREs to set up, and domain experts\n   to use confidently.\n3. They requiring hopping from tool to tool (logs, session replay, APM,\n   exceptions, etc.) to stitch together the clues yourself.\n\nWe hope you give HyperDX in ClickStack a try and let us know how we're doing!\n\n## Contact\n\n- [Open an Issue](https:\u002F\u002Fgithub.com\u002Fhyperdxio\u002Fhyperdx\u002Fissues\u002Fnew)\n- [Discord](https:\u002F\u002Fdiscord.gg\u002FFErRRKU78j)\n- [Email](mailto:support@hyperdx.io)\n\n## HyperDX Usage Data\n\nHyperDX collects anonymized usage data for open source deployments. This data\nsupports our mission for observability to be available to any team and helps\nsupport our open source product run in a variety of different environments.\nWhile we hope you will continue to support our mission in this way, you may opt\nout of usage data collection by setting the `USAGE_STATS_ENABLED` environment\nvariable to `false`. Thank you for supporting the development of HyperDX!\n\n## License\n\n[MIT](\u002FLICENSE)\n","HyperDX 是一个开源的可观测性平台，它集成了会话回放、日志、指标、跟踪和错误等功能，旨在帮助工程师快速解决生产环境中的问题。该项目基于 ClickHouse 和 OpenTelemetry 构建，支持对日志和追踪数据进行高效搜索与可视化，并且能够跨多种数据源（如会话回放、指标等）进行关联分析。其特色还包括直观的全文及属性搜索语法、无需复杂查询语言即可创建高基数事件仪表盘以及开箱即用的告警设置功能。HyperDX 适用于需要实时监控应用性能、排查线上故障或优化用户体验的各种场景，尤其适合那些已经采用 ClickHouse 作为数据存储方案的技术团队使用。",2,"2026-06-11 03:25:13","top_topic"]