Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

[Feature] Trace Pipeline Support in BanyanDB

Abierto
  • ¿Algo no está bien?
#13,634 1 comentario 2 reacciones 3 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

@hanahmily ya está trabajando en esto.

Desde el 25/12/2025.

Evaluación

Este issue todavía no se ha evaluado.

Descripción

database feature
Search before asking
  • I had searched in the issues and found no similar feature requirement.
Description

🌟 Feature Request: Trace Pipeline Support in BanyanDB (Target: v0.11)

Summary

Introduce a trace pipeline framework into BanyanDB to enable trace-oriented processing, sampling, and enrichment directly within the database layer.
The pipeline will serve as the foundation for intelligent, context-aware trace handling—allowing dynamic update, analysis, and retention decisions while preserving schema and performance guarantees.

Background

BanyanDB currently supports efficient ingestion and querying of trace data, but processing is span-oriented and lacks capabilities for post-ingestion, trace-level operations.

Modern observability scenarios—such as tail-based sampling, cross-service trace enrichment, or behavioral trace analysis—require the database to treat a group of spans (sharing the same trace ID) as one logical unit.

Introducing a trace pipeline provides a structured mechanism to:

  • Analyze and modify trace data after ingestion.
  • Aggregate spans consistently, regardless of their reported order or source.
  • Make smarter data retention decisions based on complete trace context.
Goal

Deliver a trace-level pipeline mechanism that:

  1. Processes collected spans as unified trace entities in best-effort strategy(No 100% guaranteed).
  2. Supports runtime enrichment and analysis of existing tag values, further considering to declear trace-level schema, e.g. trace latency.
  3. Maintains persistent file-based processor context across ingestion batches for continuity and scale.
  4. Enables tail-based sampling via a reserved deletion/retention flag.
  5. Integrates cleanly with OAP for schema declaration, dynamic loading, and test validation.
Use case

This issue includes several key features and use cases, mostly around trace post-analysis, e.g., tail sampling.

Most things were discussed between @hanahmily and me at a high level. No detail is confirmed yet.

Related issues

No response

Are you willing to submit a pull request to implement this on your own?
  • Yes I am willing to submit a pull request on my own!
Code of Conduct
Lenguaje dominante
Java
Estrellas
25k
Forks
6.6k
Merge medio
13 h 9 min
PR fusionados (30 d)
23

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de apache/skywalking

Todos los issues de apache/skywalking

Issues similares

Más issues de Java

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.