Potential fix for pull request finding

Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
1 file changed
tree: ce25949f08154cccb13b32f2f1b02f6c157773b7
  1. .github/
  2. api/
  3. assets/
  4. banyand/
  5. bydbctl/
  6. canopy/
  7. cmd/
  8. dist/
  9. docs/
  10. fodc/
  11. mcp/
  12. pkg/
  13. scripts/
  14. skills/
  15. test/
  16. ui/
  17. .asf.yaml
  18. .dlc.json
  19. .gitattributes
  20. .gitignore
  21. .golangci-format.yml
  22. .golangci.yml
  23. .licenserc.yaml
  24. AGENTS.md
  25. CHANGES.md
  26. CONTRIBUTING.md
  27. go.mod
  28. go.sum
  29. LICENSE
  30. Makefile
  31. NOTICE
  32. README.md
  33. revive.toml
  34. test_table
README.md

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.