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

Clone this repo:
  1. e1ba421 Support client watch the schema server updates (#995) by mrproliu · 10 hours ago main
  2. 168dcae Adding both etcd and property schema test in each E2E (#994) by mrproliu · 34 hours ago
  3. 0959cab ignore backup if no segments in the storage (#992) by mrproliu · 2 days ago
  4. 54b7a64 Fix sidx tag filter range check issue (#991) by Gao Hongtao · 4 days ago
  5. a9d081b chore: update dependencies and versions in go.mod, go.sum, and package-lock.json (#986) by Gao Hongtao · 5 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.