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

Clone this repo:
  1. 75bf904 Fix property schema client connection not stable after data node restarted (#1038) by mrproliu · 8 hours ago main
  2. d590125 fix(measure): always enforce query time range in index-mode inverted search (#1037) by Gao Hongtao · 10 hours ago
  3. ccede53 fix(mcp): Add explicit validation for properties and tools, and harden the server (#1036) by Fine0830 · 15 hours ago
  4. 594717b fix(sidx): stabilize tag filter matching order (#1034) by Gao Hongtao · 32 hours ago
  5. d3aca84 Make FODC agent test more stable (#1033) by mrproliu · 34 hours 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.