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

Clone this repo:
  1. d613e58 Fix bugs time query range will not automatically update and add some new time query ranges (#757) by peachisai · 10 hours ago main
  2. d0942a3 Fix query access log unmarshal error (#756) by mrproliu · 2 days ago
  3. 5741ebd Enhance query access logging across gRPC services (#755) by Gao Hongtao · 3 days ago
  4. eaf69c3 fix panic when repair property (#753) by mrproliu · 3 days ago
  5. 6beafa0 Add query access log support (#754) by Gao Hongtao · 3 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.