selfhost.directory

The index of self-hostable projects — ranked, categorized and served with live updates.
Own your data and stop giving it to big tech.

hypertrace logo

Self-host hypertrace

0.2.8

Open-source distributed tracing & observability platform

BetaOpen CoreOther
Updatedlast year
LanguageShell
Setup difficultyAdvanced
Stars
519
CPU
3 CPUs
RAM
4GB Memory
Ports
2020 (Hypertrace UI), 4317 (OTLP gRPC collector), 55681 (OTLP HTTP collector), 14268 (Jaeger HTTP collector), 9411 (Zipkin HTTP collector)
Requires
Apache Kafka, Apache Pinot, Apache ZooKeeper, MongoDB
Docker
hypertrace/hypertrace
Install with Docker Compose

What is hypertrace?

Hypertrace is a cloud-native observability platform built by Traceable that ingests traces from OpenTelemetry, Jaeger, and Zipkin without requiring code changes. It provides service graph visualization, custom dashboards, real-time metrics aggregation, root cause analysis, and roll-out monitoring. Deployment options include Docker Compose for local testing and Helm charts for Kubernetes production clusters. The project follows an open-core model: the core tracing engine is Apache 2.0 licensed, while advanced features like service graphs and metrics are under the Traceable Community License (source-available). Minimum requirements are 3 CPUs and 4GB RAM.

Should you self-host hypertrace?

hypertrace scores 45/100 on selfhost.directory (how scoring works) and ranks #9 of 9 in Application Performance Monitoring. It has 519 GitHub stars.

There was no stable release in the past 12 months, so check the repository's recent activity before you rely on it.

Setup is advanced: plan for several services and some ongoing maintenance. An official Docker image is available. It is Other-licensed and written mostly in Shell.

Its closest alternative on selfhost.directory is sentry (80/100, 45 669 stars). It scores higher overall, so compare the two before you pick. See hypertrace vs sentry side by side.

Features

  • 100% trace ingestion (no sampling)
  • Backend performance monitoring
  • Custom dashboards
  • Distributed Tracing
  • Docker Compose local deployment
  • Multi-format trace ingestion
  • Real-time metrics aggregation
  • Roll-out monitoring
  • Root Cause Analysis
  • Service Graph
  • Service health overview

hypertrace README

How to install hypertrace

Install hypertrace with Docker Compose

Environment variables
MONGO_HOST, ZK_CONNECT_STR, EXPORTER_KAFKA_BROKER, EXPORTER_KAFKA_TOPIC, KAFKA_BOOTSTRAP_SERVERS, DEFAULT_TENANT_ID, SPAN_GROUPBY_SESSION_WINDOW_INTERVAL, REPLICATION_FACTOR, ENTITY_SERVICE_HOST_CONFIG, ENTITY_SERVICE_PORT_CONFIG, ATTRIBUTE_SERVICE_HOST_CONFIG, ATTRIBUTE_SERVICE_PORT_CONFIG, CONFIG_SERVICE_HOST_CONFIG, CONFIG_SERVICE_PORT_CONFIG, NUM_STREAM_THREADS, PRE_CREATE_TOPICS, PRODUCER_VALUE_SERDE, LOG_LEVEL

git clone https://github.com/hypertrace/hypertrace.git cd hypertrace/docker docker-compose pull docker-compose up --force-recreate

Requires Docker Desktop with 4GB memory and 4 CPUs recommended

How to configure hypertrace

  • ATTRIBUTE_SERVICE_HOST_CONFIGhypertraceAttribute service host

    Attribute service host

  • ATTRIBUTE_SERVICE_PORT_CONFIG9001Attribute service port

    Attribute service port

  • CONFIG_SERVICE_HOST_CONFIGhypertraceConfig service host

    Config service host

  • CONFIG_SERVICE_PORT_CONFIG9001Config service port

    Config service port

  • DEFAULT_TENANT_ID__defaultDefault tenant ID

    Default tenant ID

  • ENTITY_SERVICE_HOST_CONFIGhypertraceEntity service host

    Entity service host

  • ENTITY_SERVICE_PORT_CONFIG9001Entity service port

    Entity service port

  • EXPORTER_KAFKA_BROKERKafka broker for trace export

    Kafka broker for trace export

  • EXPORTER_KAFKA_TOPICKafka topic for Jaeger spans

    Kafka topic for Jaeger spans

  • KAFKA_BOOTSTRAP_SERVERSKafka bootstrap servers

    Kafka bootstrap servers

  • LOG_LEVELerrorPinot log level

    Pinot log level

  • MONGO_HOSTMongoDB host for document store

    MongoDB host for document store

  • NUM_STREAM_THREADS1Number of stream threads

    Number of stream threads

  • PRE_CREATE_TOPICStruePre-create Kafka topics

    Pre-create Kafka topics

  • PRODUCER_VALUE_SERDEorg.hypertrace.core.kafkastreams.framework.serdes.GenericAvroSerdeProducer value serde class

    Producer value serde class

  • REPLICATION_FACTOR1Kafka replication factor

    Kafka replication factor

  • SPAN_GROUPBY_SESSION_WINDOW_INTERVAL2Session window interval for span grouping

    Session window interval for span grouping

  • ZK_CONNECT_STRZooKeeper connection string

    ZooKeeper connection string

hypertrace releases & version history

FAQ

What software license does Hypertrace use?

Hypertrace Core uses Apache 2.0 license, while Hypertrace Community Edition uses the Traceable Community License (source-available).

What changes do I need to make in my application if I am already using Jaeger, Zipkin or OpenTelemetry?

No changes needed - Hypertrace accepts all major trace data formats natively, so existing instrumentation works immediately.

Who created Hypertrace?

Hypertrace was originally developed by Traceable as a highly scalable distributed tracing platform for their cloud-native application security platform.

What is Distributed Tracing?

Distributed tracing tracks a network request as it travels through services in a microservices architecture to troubleshoot latency and failures.

What is Hypertrace?

Hypertrace is a highly scalable distributed tracing and observability platform designed to ingest and analyze large volumes of production trace data using OpenTelemetry-based agents.

More in Application Performance Monitoring

Rate this project

Click to rate — no account needed.

0 comments

Posting as guest
Loading comments…