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

Clone this repo:
  1. 0af505e feat: Add `NoSort` Field to IndexRule page (#568) by Fine0830 · 6 hours ago main
  2. b9de1f4 Add `indexMode` to display on the measure page (#567) by Fine0830 · 22 hours ago
  3. 1dc9198 Fix View Configuration and remove redundant fields on Property page (#566) by Fine0830 · 29 hours ago
  4. 3d44bf9 refactor: Add a common component to avoid hard code (#565) by Fine0830 · 29 hours ago
  5. 1488025 docs: Add `Setting up Environment Variables` in README (#564) by Fine0830 · 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.