jaeger alternatives and similar packages
Based on the "Database" category.
Alternatively, view jaeger alternatives based on common mentions on social networks and blogs.
prometheus10.0 9.8 jaeger VS prometheusThe Prometheus monitoring system and time series database.
influxdb9.9 9.4 jaeger VS influxdbScalable datastore for metrics, events, and real-time analytics
tidb9.9 10.0 jaeger VS tidbTiDB is an open-source, cloud-native, distributed, MySQL-Compatible database for elastic scale and real-time analytics. Try AI-powered Chat2Query free at : https://tidbcloud.com/free-trial
cockroach9.9 10.0 jaeger VS cockroachCockroachDB - the open source, cloud-native distributed SQL database.
dgraph9.8 3.6 jaeger VS dgraphNative GraphQL Database with graph backend
bolt9.8 0.0 jaeger VS boltA low-level key/value database for Go.
Milvus9.8 9.9 jaeger VS MilvusVector database for scalable similarity search and AI applications.
vitess9.8 9.9 jaeger VS vitessVitess is a database clustering system for horizontal scaling of MySQL.
dolt9.7 10.0 jaeger VS doltDolt – Git for Data
badger9.7 8.1 jaeger VS badgerFast key-value DB in Go.
TinyGo9.7 9.3 jaeger VS TinyGoGo compiler for small places. Microcontrollers, WebAssembly (WASM/WASI), and command-line tools. Based on LLVM.
rqlite9.7 8.2 jaeger VS rqliteThe lightweight, distributed relational database built on SQLite
groupcache9.7 0.0 jaeger VS groupcachegroupcache is a caching and cache-filling library, intended as a replacement for memcached in many cases.
migrate9.6 7.2 jaeger VS migrateDatabase migrations. CLI and Golang library.
VictoriaMetrics9.5 9.9 jaeger VS VictoriaMetricsVictoriaMetrics: fast, cost-effective monitoring solution and time series database
noms9.5 1.9 jaeger VS nomsThe versioned, forkable, syncable database
pgweb9.5 6.2 jaeger VS pgwebCross-platform client for PostgreSQL databases
Tile389.5 5.7 jaeger VS Tile38Real-time Geospatial and Geofencing
kingshard9.5 0.0 jaeger VS kingshardA high-performance MySQL proxy
sqlc9.4 8.6 jaeger VS sqlcGenerate type-safe code from SQL
go-cache9.4 0.0 jaeger VS go-cacheAn in-memory key:value store/cache (similar to Memcached) library for Go, suitable for single-machine applications.
immudb9.4 9.6 jaeger VS immudbimmudb - immutable database based on zero trust, SQL and Key-Value, tamperproof, data change history
goleveldb9.3 6.4 jaeger VS goleveldbLevelDB key/value database in Go.
BigCache9.3 6.7 jaeger VS BigCacheEfficient cache for gigabytes of data written in Go.
dtm9.3 9.8 jaeger VS dtm此仓库应常青藤爸爸要求，已停止维护，请移步 https://github.com/dtm-labs/dtf
bbolt9.3 0.0 jaeger VS bboltAn embedded key/value database for Go.
go-mysql9.2 7.4 jaeger VS go-mysqla powerful mysql toolset with Go
Squirrel9.2 1.6 jaeger VS SquirrelFluent SQL generation for golang
bytebase9.1 9.8 jaeger VS bytebaseDatabase CI/CD for DevOps teams. https://www.bytebase.com
go-mysql-elasticsearch9.1 0.0 jaeger VS go-mysql-elasticsearchSync MySQL data into elasticsearch
ledisdb9.0 0.0 jaeger VS ledisdbA high performance NoSQL Database Server powered by Go
buntdb9.0 3.1 jaeger VS buntdbBuntDB is an embeddable, in-memory key/value database for Go with custom indexing and geospatial support
pREST8.9 4.5 jaeger VS pRESTPostgreSQL ➕ REST, low-code, simplify and accelerate development, ⚡ instant, realtime, high-performance on any Postgres application, existing or new
rosedb8.9 9.1 jaeger VS rosedb🚀 A high performance NoSQL database based on bitcask, supports string, list, hash, set, and sorted set.
go-memdb8.8 0.0 jaeger VS go-memdbGolang in-memory database built on immutable radix trees
xo8.8 3.6 jaeger VS xoCommand line tool to generate idiomatic Go code for SQL databases supporting PostgreSQL, MySQL, SQLite, Oracle, and Microsoft SQL Server
tiedot8.7 0.9 jaeger VS tiedotA rudimentary implementation of a basic document (NoSQL) database in Go
sql-migrate8.6 4.1 jaeger VS sql-migrateSQL schema migration tool for Go.
nutsdb8.6 8.7 jaeger VS nutsdbA simple, fast, embeddable, persistent key/value store written in pure Go. It supports fully serializable transactions and many data structures such as list, set, sorted set.
dbmate8.6 3.9 jaeger VS dbmate:rocket: A lightweight, framework-agnostic database migration tool.
cache2go8.5 3.2 jaeger VS cache2goConcurrency-safe Go caching library with expiration capabilities and access counters
GCache8.4 0.0 jaeger VS GCacheAn in-memory cache library for golang. It supports multiple eviction policies: LRU, LFU, ARC
atlas8.4 0.0 jaeger VS atlasA modern tool for managing database schemas
gocraft/dbr (database records)Additions to Go's database/sql for super fast performance and convenience.
goqu8.1 0.0 jaeger VS goquSQL builder and query library for golang
fastcache8.1 1.6 jaeger VS fastcacheFast thread-safe inmemory cache for big number of entries in Go. Minimizes GC overhead
CovenantSQL8.0 0.0 jaeger VS CovenantSQLA decentralized, trusted, high performance, SQL database with blockchain features
gendry8.0 0.0 jaeger VS gendrya golang library for sql builder
chproxy7.8 7.7 jaeger VS chproxyOpen-Source ClickHouse http proxy and load balancer
diskv7.7 0.0 jaeger VS diskvA disk-backed key-value store.
Access the most powerful time series database as a service
Do you think we are missing an alternative of jaeger or a related project?
Jaeger - a Distributed Tracing System
graph TD LIB --> |HTTP or gRPC| COLLECTOR LIB[Jaeger Client] --> |UDP| AGENT[Jaeger Agent] %% AGENT --> |HTTP/sampling| LIB AGENT --> |gRPC| COLLECTOR[Jaeger Collector] %% COLLECTOR --> |gRPC/sampling| AGENT SDK[OpenTelemetry SDK] --> |UDP| AGENT SDK --> |HTTP or gRPC| COLLECTOR COLLECTOR --> STORE[Storage] COLLECTOR --> |gRPC| PLUGIN[Storage Plugin] PLUGIN --> STORE QUERY[Jaeger Query Service] --> STORE QUERY --> |gRPC| PLUGIN UI[Jaeger UI] --> |HTTP| QUERY subgraph Application Host subgraph User Application LIB SDK end AGENT end
Jaeger, inspired by Dapper and OpenZipkin, is a distributed tracing platform created by Uber Technologies and donated to Cloud Native Computing Foundation. It can be used for monitoring microservices-based distributed systems:
- Distributed context propagation
- Distributed transaction monitoring
- Root cause analysis
- Service dependency analysis
- Performance / latency optimization
- Jaeger documentation for getting started, operational details, and other information.
- Blog post Evolving Distributed Tracing at Uber.
- Tutorial / walkthrough Take Jaeger for a HotROD ride.
Jaeger is hosted by the Cloud Native Computing Foundation (CNCF) as the 7th top-level project (graduated in October 2019). If you are a company that wants to help shape the evolution of technologies that are container-packaged, dynamically-scheduled and microservices-oriented, consider joining the CNCF. For details about who's involved and how Jaeger plays a role, read the CNCF Jaeger incubation announcement and Jaeger graduation announcement.
Jaeger is an open source project with open governance. We welcome contributions from the community, and we would love your help to improve and extend the project. Here are some ideas for how to get involved. Many of them do not even require any coding.
Jaeger backend is designed to have no single points of failure and to scale with the business needs. For example, any given Jaeger installation at Uber is typically processing several billions of spans per day.
Native support for OpenTracing
Jaeger backend, Web UI, and instrumentation libraries have been designed from the ground up to support the OpenTracing standard.
- Represent traces as directed acyclic graphs (not just trees) via span references
- Support strongly typed span tags and structured logs
- Support general distributed context propagation mechanism via baggage
Jaeger project recommends OpenTelemetry SDKs for instrumentation, instead of Jaeger's native SDKs that are now deprecated.
The OpenTracing and OpenCensus projects have merged into a new CNCF project called OpenTelemetry. The Jaeger and OpenTelemetry projects have different goals. OpenTelemetry aims to provide APIs and SDKs in multiple languages to allow applications to export various telemetry data out of the process, to any number of metrics and tracing backends. The Jaeger project is primarily the tracing backend that receives tracing telemetry data and provides processing, aggregation, data mining, and visualizations of that data. The Jaeger client libraries do overlap with OpenTelemetry in functionality. OpenTelemetry natively supports Jaeger as a tracing backend and makes Jaeger native clients unnecessary. For more information please refer to a blog post Jaeger and OpenTelemetry.
Multiple storage backends
Jaeger can be used with a growing a number of storage backends:
- It natively supports two popular open source NoSQL databases as trace storage backends: Cassandra and Elasticsearch.
- It integrates via a gRPC API with other well known databases that have been certified to be Jaeger compliant: TimescaleDB via Promscale, ClickHouse.
- There is embedded database support using Badger and simple in-memory storage for testing setups.
- There are ongoing community experiments using other databases, such as ScyllaDB, InfluxDB, Amazon DynamoDB.
Modern Web UI
Cloud Native Deployment
Jaeger backend is distributed as a collection of Docker images. The binaries support various configuration methods, including command line options, environment variables, and configuration files in multiple formats (yaml, toml, etc.) Deployment to Kubernetes clusters is assisted by Kubernetes templates and a Helm chart.
All Jaeger backend components expose Prometheus metrics by default (other metrics backends are also supported). Logs are written to standard out using the structured logging library zap.
Third-party security audits of Jaeger are available in https://github.com/jaegertracing/security-audits. Please see Issue #1718 for the summary of available security mechanisms in Jaeger.
Backwards compatibility with Zipkin
Although we recommend instrumenting applications with OpenTelemetry, if your organization has already invested in the instrumentation using Zipkin libraries, you do not have to rewrite all that code. Jaeger provides backwards compatibility with Zipkin by accepting spans in Zipkin formats (Thrift or JSON v1/v2) over HTTP. Switching from Zipkin backend is just a matter of routing the traffic from Zipkin libraries to the Jaeger backend.
Version Compatibility Guarantees
Occasionally, CLI flags can be deprecated due to, for example, usability improvements or new functionality. In such situations, developers introducing the deprecation are required to follow [these guidelines](./CONTRIBUTING.md#deprecating-cli-flags).
In short, for a deprecated CLI flag, you should expect to see the following message in the
(deprecated, will be removed after yyyy-mm-dd or in release vX.Y.Z, whichever is later)
A grace period of at least 3 months or two minor version bumps (whichever is later) from the first release containing the deprecation notice will be provided before the deprecated CLI flag can be deleted.
For example, consider a scenario where v1.28.0 is released on 01-Jun-2021 containing a deprecation notice for a CLI flag. This flag will remain in a deprecated state until the later of 01-Sep-2021 or v1.30.0 where it can be removed on or after either of those events. It may remain deprecated for longer than the aforementioned grace period.
- Published: https://www.jaegertracing.io/docs/
- Source: https://github.com/jaegertracing/documentation
Jaeger project recommends OpenTelemetry SDKs for instrumentation, instead of Jaeger's native SDKs that are now deprecated.
Building From Source
Thanks to all the people who already contributed!
Rules for becoming a maintainer are defined in the [GOVERNANCE](./GOVERNANCE.md) document.
Below are the official maintainers of the Jaeger project.
@jaegertracing/jaeger-maintainers to tag them on issues / PRs.
Some repositories under jaegertracing org have additional maintainers.
We are grateful to our former maintainers for their contributions to the Jaeger project.
Project Status Meetings
The Jaeger maintainers and contributors meet regularly on a video call. Everyone is welcome to join, including end users. For meeting details, see https://www.jaegertracing.io/get-in-touch/.
Get in Touch
Have questions, suggestions, bug reports? Reach the project community via these channels:
- Slack chat room
#jaeger(need to join CNCF Slack for the first time)
- GitHub issues and discussions
Jaeger as a product consists of multiple components. We want to support different types of users, whether they are only using our instrumentation libraries or full end to end Jaeger installation, whether it runs in production or you use it to troubleshoot issues in development.
Please see [ADOPTERS.md](./ADOPTERS.md) for some of the organizations using Jaeger today. If you would like to add your organization to the list, please comment on our survey issue.
Copyright (c) The Jaeger Authors. [Apache 2.0 License](./LICENSE).
*Note that all licence references and agreements mentioned in the jaeger README section above are relevant to that project's source code only.