<a href="https://github.com/hypertrace/hypertrace/issues">Report Bug</a> <a href="https://github.com/hypertrace/hypertrace/issues">Request Feature</a>
CVE-2021-44228 and CVE-2021-45046 disclosed security vulnerabilities in the Apache Log4j 2 version 2.15 or below.
We have upgraded all the dependent hypertrace repositories and have cut the new release with a safe version of Log4j (2.17). We strongly encourage upgrading to the latest version (v0.2.7) of hypertrace or using appropriate charts from the latest release.
Hypertrace is a cloud-native distributed tracing based Observability platform that gives visibility into your dev and production distributed systems.
Hypertrace converts distributed trace data into relevant insight for everyone. Infrastructure teams can identify which services are causing overload. Service teams can diagnose why a specific user's request failed, or which applications put their service objectives at risk. Deployment teams can know if a new version is causing a problem.
With Hypertrace you can,
|![Product Name Screen Shot][product-screenshot]|
If you want to see Hypertrace in action, you can quickly start Hypertrace.
2 GBof memory to
4 GBof memory, and set CPUs to at least 4 CPUs.
git clone https://github.com/hypertrace/hypertrace.git cd hypertrace/docker docker-compose pull docker-compose up --force-recreate
This will start all services required for Hypertrace. Once you see the service
Hypertrace-UI start, you can visit the UI at http://localhost:2020.
If your application is already instrumented to send traces to Zipkin or Jaeger, it will work with Hypertrace.
If not, you can try Hypertrace with our sample application by running
docker-compose -f docker-compose-zipkin-example.yml up
the sample app will run at http://localhost:8081. You should request the URL a few times to generate some sample trace requests!
We support helm charts to simplify deploying Hypertrace in Kubernetes environment, maybe on your on-premise server or cloud instance!
Please refer to the deployments section in our documentation which lists the steps to deploy Hypertrace on different Kubernetes flavors across different operating systems and cloud providers. You can find the Helm Charts and installation scripts with more details here.
Note: We have created
hypertrace-service to simplify local deployment and quick-start with Hypertrace. As of now, we don't support them for production because of some limitations and some unreliabiliy with scaling. So, we will encourage you to deploy individual components for staging as well as production deployments.
Released versions of Docker images for various Hypertrace components are available on dockerhub.
See the open issues for a list of proposed features (and known issues).
Contributions are what make the open community such an amazing place to be learn, inspire, and create. Any contributions you make are greatly appreciated. Check out our Contribution Guidelines for more details.
Hypertrace follows the open core model where "Hypertrace core" (or simply Core) is made available under the Apache 2.0 license, which has distributed trace ingestion and exploration features. The Services, Endpoints, Backends and Service Graph features of Hypertrace Community Edition are made available under the Traceable Community license.