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

Clone this repo:
  1. c827067 Fix topn query nil and add more context to err (#445) by Gao Hongtao · 4 days ago main
  2. 5eb5486 Switch e2e image repo to ghcr (#444) by Gao Hongtao · 9 days ago v0.6.0
  3. a091ac0 Change default null value (#443) by Gao Hongtao · 9 days ago
  4. acd2f4c Long running testing (#442) by Gao Hongtao · 10 days ago
  5. 3f57397 Bump Go Node and Dependencies (#441) by Gao Hongtao · 3 weeks 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.