declarative config: baggage processor

[zeitlinger]

Component(s)

processors

Is your feature request related to a problem? Please describe.

port BaggageProcessorCustomizer to declarative config

Blocked by open-telemetry/opentelemetry-java#7480

[zeitlinger]

@jack-berg this component uses otel.java.experimental.span-attributes.

• where does it belong in the config file
• I suggest we add a mapping rule to add declarative config bridge opentelemetry-java#7480

[jack-berg]

The most natural way for this to appear in declarative config would be to treat it as a span processor which can be added to the list of span processors by name. Naively, something like:

tracer_provider:
  processors:
    - baggage:
         attribute_keys:
           - foo
           - bag
    - batch:
         exporter:
           otlp_http:

Of course, we'd want to more closely consider the config interface, with potential options for things like allow lists, disallow lists, and pattern matching. This type of thing is a recurring concept in declarative config so we have some modeling guidance around this which baggage processor could incorporate: https://github.com/open-telemetry/opentelemetry-configuration/blob/main/validator/internal#properties-which-pattern-matching

[zeitlinger]

I think this is the correct link: https://github.com/open-telemetry/opentelemetry-configuration/blob/main/CONTRIBUTING.md#properties-which-pattern-matching

[zeitlinger]

This class can be reused: open-telemetry/opentelemetry-java@cecfb83#diff-76b53497c608df0376ebc21713fd62454423a8606ac038f7b8242cdcaffdade9 - it'll be available with 2.18.0-alpha instrumentation bom