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

Clone this repo:
  1. 5898e90 Fix sampling for traces split across blocks (#1240) by Gao Hongtao · 6 hours ago main
  2. 6c51a54 canopy: use the in-repo setup-build-env composite for the image job (#1239) by Gao Hongtao · 7 hours ago
  3. 0422b1b Fix trace fragment sampling across partial merges (#1237) by Gao Hongtao · 27 hours ago
  4. cb9814a canopy: docker image, makefile toolchain, CI integration tests (standalone + distributed) (#1238) by Gao Hongtao · 28 hours ago
  5. 0c91de5 canopy: query console + result-view fixes for distributed clusters, verification checklist (#1236) by Gao Hongtao · 2 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.