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

Clone this repo:
  1. ccbfd1f Support writing stream and trace data with specifications (#888) by Huang Youliang · 2 days ago main
  2. 7dcd935 Add First Occurrence Data Collection (FODC) doc (#895) by 吴晟 Wu Sheng · 3 days ago
  3. 41cf3a2 docs(fodc): document the Watchdog And Flight Recorder Development Design for FODC (#892) by Fine0830 · 3 days ago
  4. 09485f4 Fix incorrect key range update in sidx part metadata (#891) by Gao Hongtao · 5 days ago
  5. 8c647e9 internal TLS reload (#882) by OmCheeLin · 6 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.