Bridge Bento Processing into Distributed Traces #20

Problem

Bento operates as a "middleware" between NATS and ClickHouse. If Bento transformations are slow or failing, those errors appear as isolated events. We need these transformations to show up as "Child Spans" directly under the original API ingestion trace.

Proposed Solution

Configure the Bento OTel component to respect incoming tracing headers.

• Ensure Bento is initialized with the same TracerProvider as the Go app.
• Use the tracing processor in Bento to ensure that as events move through "Pipes," they maintain the original Trace ID.

Alternatives Considered

None

Additional Context

This allows a developer to see: API Request -> NATS Publish -> Bento Pipe Transformation -> ClickHouse Insert all in one single Gantt chart in SigNoz.