An open source distributed tracing & observability platform!
Explore the docs »
Visit our blog
·
Report Bug
·
Request Feature
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,
- Perform Root cause analysis(RCA) whenever something breaks in your system.
- Watch roll-outs and compare key metrics.
- Determine performance bottlenecks and identify slow operations like slow API calls or DB queries.
- Monitor microservice dependencies and Observe your applications.
 |
|---|
| Hypertrace |
If you want to see Hypertrace in action, you can quickly start Hypertrace.
- docker-engine (17.12.0+)
- docker-compose (1.21.0 +)
- We recommend you change the Docker Desktop default settings from
2 GBof memory to4 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-recreateThis 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 upthe 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-ingester and 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.
- Join the Hypertrace Workspace on Slack to connect with other users, contributors and people behind Hypertrace.
- We have public monthly meeting on last Thursday of the month at 8:00 AM PST/ 8:30 PM IST/ 11:00 AM ET/ 5:00 PM CET where we try to give our community a holistic overview of new features in Hypertrace and community activities. We would like to hear feedback, discuss feature requests and also help new contributors to get started with contributing to Open Source projects. You can join the zoom meeting here or use zoom meeting details as below:
- Meeting ID: 990 5679 8944
- Passcode: 111111
- If you want to discuss any ideas or have any questions or show us how you are using Hypertrace, you can use GitHub discsussions as well.
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 source 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.