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

Clone this repo:
  1. aa87b5f Suppport backup and restore trace data (#831) by mrproliu · 2 days ago main
  2. 41eef28 Fix Several Flaws of Trace Query (#830) by Gao Hongtao · 2 days ago
  3. 0eff0fb Fix the property repair UT (#825) by mrproliu · 3 days ago
  4. c6dd7e8 feat(UI): Implement the Query Page for BydbQL (#829) by Fine0830 · 3 days ago
  5. 6155fa0 fix missing HTTP endpoint of bydbQL (#827) by mrproliu · 4 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.