base on Resolve production issues, fast. An open source observability platform unifying session replays, logs, metrics, traces and errors powered by Clickhouse and OpenTelemetry. <p align="center"> <a href="https://hyperdx.io"> <picture> <source media="(prefers-color-scheme: dark)" srcset="./.github/images/logo_dark.png#gh-dark-mode-only"> <img alt="hyperdx logo" src="./.github/images/logo_light.png#gh-light-mode-only"> </picture> </a> </p> --- # HyperDX [HyperDX](https://hyperdx.io), a core component of [ClickStack](https://clickhouse.com/use-cases/observability), 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). <p align="center"> <a href="https://clickhouse.com/docs/use-cases/observability/clickstack/overview">Documentation</a> • <a href="https://hyperdx.io/discord">Chat on Discord</a> • <a href="https://play.hyperdx.io/search">Live Demo</a> • <a href="https://github.com/hyperdxio/hyperdx/issues/new">Bug Reports</a> • <a href="./CONTRIBUTING.md">Contributing</a> • <a href="https://clickhouse.com/use-cases/observability">Website</a> </p> - 🕵️ 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) <br/> <img alt="Search logs and traces all in one place" src="./.github/images/search_splash.png" title="Search logs and traces all in one place"> ## Spinning Up HyperDX HyperDX can be deployed as part of ClickStack, which includes ClickHouse, HyperDX, OpenTelemetry Collector and MongoDB. ```bash 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](https://clickhouse.com/docs/use-cases/observability/clickstack/deployment). > 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](https://console.clickhouse.cloud/signUp) 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](https://clickhouse.com/docs/use-cases/observability/clickstack/sdks/browser), [Node.js](https://clickhouse.com/docs/use-cases/observability/clickstack/sdks/nodejs), and [Python](https://clickhouse.com/docs/use-cases/observability/clickstack/sdks/python) You can find the full list in [our docs](https://clickhouse.com/docs/use-cases/observability/clickstack). **OpenTelemetry** Additionally, HyperDX is compatible with [OpenTelemetry](https://opentelemetry.io/), 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](https://opentelemetry.io/docs/instrumentation/)) 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](./CONTRIBUTING.md)) - [Submitting feature requests or bugs](https://github.com/hyperdxio/hyperdx/issues/new) - Improving our product or contribution documentation - Voting on [open issues](https://github.com/hyperdxio/hyperdx/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: 1. 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. 2. They're hard to use, requiring full-time SREs to set up, and domain experts to use confidently. 3. 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 - [Open an Issue](https://github.com/hyperdxio/hyperdx/issues/new) - [Discord](https://discord.gg/FErRRKU78j) - [Email](mailto:[email protected]) ## 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! ## License [MIT](/LICENSE) ", Assign "at most 3 tags" to the expected json: {"id":"2030","tags":[]} "only from the tags list I provide: [{"id":77,"name":"3d"},{"id":89,"name":"agent"},{"id":17,"name":"ai"},{"id":54,"name":"algorithm"},{"id":24,"name":"api"},{"id":44,"name":"authentication"},{"id":3,"name":"aws"},{"id":27,"name":"backend"},{"id":60,"name":"benchmark"},{"id":72,"name":"best-practices"},{"id":39,"name":"bitcoin"},{"id":37,"name":"blockchain"},{"id":1,"name":"blog"},{"id":45,"name":"bundler"},{"id":58,"name":"cache"},{"id":21,"name":"chat"},{"id":49,"name":"cicd"},{"id":4,"name":"cli"},{"id":64,"name":"cloud-native"},{"id":48,"name":"cms"},{"id":61,"name":"compiler"},{"id":68,"name":"containerization"},{"id":92,"name":"crm"},{"id":34,"name":"data"},{"id":47,"name":"database"},{"id":8,"name":"declarative-gui "},{"id":9,"name":"deploy-tool"},{"id":53,"name":"desktop-app"},{"id":6,"name":"dev-exp-lib"},{"id":59,"name":"dev-tool"},{"id":13,"name":"ecommerce"},{"id":26,"name":"editor"},{"id":66,"name":"emulator"},{"id":62,"name":"filesystem"},{"id":80,"name":"finance"},{"id":15,"name":"firmware"},{"id":73,"name":"for-fun"},{"id":2,"name":"framework"},{"id":11,"name":"frontend"},{"id":22,"name":"game"},{"id":81,"name":"game-engine "},{"id":23,"name":"graphql"},{"id":84,"name":"gui"},{"id":91,"name":"http"},{"id":5,"name":"http-client"},{"id":51,"name":"iac"},{"id":30,"name":"ide"},{"id":78,"name":"iot"},{"id":40,"name":"json"},{"id":83,"name":"julian"},{"id":38,"name":"k8s"},{"id":31,"name":"language"},{"id":10,"name":"learning-resource"},{"id":33,"name":"lib"},{"id":41,"name":"linter"},{"id":28,"name":"lms"},{"id":16,"name":"logging"},{"id":76,"name":"low-code"},{"id":90,"name":"message-queue"},{"id":42,"name":"mobile-app"},{"id":18,"name":"monitoring"},{"id":36,"name":"networking"},{"id":7,"name":"node-version"},{"id":55,"name":"nosql"},{"id":57,"name":"observability"},{"id":46,"name":"orm"},{"id":52,"name":"os"},{"id":14,"name":"parser"},{"id":74,"name":"react"},{"id":82,"name":"real-time"},{"id":56,"name":"robot"},{"id":65,"name":"runtime"},{"id":32,"name":"sdk"},{"id":71,"name":"search"},{"id":63,"name":"secrets"},{"id":25,"name":"security"},{"id":85,"name":"server"},{"id":86,"name":"serverless"},{"id":70,"name":"storage"},{"id":75,"name":"system-design"},{"id":79,"name":"terminal"},{"id":29,"name":"testing"},{"id":12,"name":"ui"},{"id":50,"name":"ux"},{"id":88,"name":"video"},{"id":20,"name":"web-app"},{"id":35,"name":"web-server"},{"id":43,"name":"webassembly"},{"id":69,"name":"workflow"},{"id":87,"name":"yaml"}]" returns me the "expected json"