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

Clone this repo:
  1. 6ecbd14 Add failover process between liaison and data nodes (#433) by Gao Hongtao · 3 days ago main
  2. a85b51c Fix issues found by distributed test (#432) by Gao Hongtao · 7 days ago enhance-docs
  3. db63f7d Add Top N Aggregation to web app (#430) by Sylvie-Wxr · 8 days ago
  4. 9aff13b docs: generate protobuf api before bydbctl build (#431) by YuNing Chen · 10 days ago
  5. d5b4543 Clean up redundant API (#429) by Gao Hongtao · 11 days 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.