An observability database aims to ingest, analyze and store Metrics, Tracing and Logging data.

Clone this repo:
  1. 0bb071a docs: add property ordering and v0.11 version table (#1083) by Gao Hongtao · 6 hours ago main
  2. fee5d5e docs: document group deletion task flow (#1081) by Tanay Paul · 24 hours ago
  3. c3fc5f8ab Fix nil pointer panic in disk monitor during early initialization (#1082) by Gao Hongtao · 27 hours ago
  4. b3e5b1e docs: update tsdb.md with the added "smeta.bin" (#1074) by OmCheeLin · 28 hours ago
  5. 9654d08 Fix stale sync request blocking watch session channel (#1080) by Gao Hongtao · 33 hours ago

BanyanDB

Continuous Integration Go Report Card GitHub release GitHub release date GoDoc

BanyanDB, as an observability database, aims to ingest, analyze and store Metrics, Tracing and Logging data. It's designed to handle observability data generated by observability platform and APM system, like Apache SkyWalking etc.

Introduction

BanyanDB, as an observability database, aims to ingest, analyze and store Metrics, Tracing, and Logging data. It's designed to handle observability data generated by Apache SkyWalking. Before BanyanDB emerges, the Databases that SkyWalking adopted are not ideal for the APM data model, especially for saving tracing and logging data. Consequently, There’s room to improve the performance and resource usage based on the nature of SkyWalking data patterns.

The database research community usually uses RUM Conjecture to describe how a database access data. BanyanDB combines several access methods to build a comprehensive APM database to balance read cost, update cost, and memory overhead.

Contact us

Documentation

Contributing

For developers who want to contribute to this project, see the Contribution Guide.

License

Apache 2.0 License.