Can opentelemetry input trace records be filtered using fluent-bit filter plugins

[srini38]

Hi,
Please let me know if opentelemetry input trace entries that are stored with fluent-bit as ctrace records could be filtered using grep or other filter plugins. For example would it be possible to filter and exclude traces from service.name: 'hello-app'?

Sample opentelemetry trace output

|-------------------- RESOURCE SPAN --------------------|
resource:
- attributes:
- service.name: 'hello-app'
- dropped_attributes_count: 0
schema_url:
[scope_span]
instrumentation scope:
- name : go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp
- version : 0.42.0
- dropped_attributes_count: 0
- attributes:

schema_url:
[spans]
     [span 'GET /hello-world']
         - trace_id                : 14e32bf39056b8cf452177dbe1d73c10
         - span_id                 : 86065bc41003298a
         - parent_span_id          : undefined
         - kind                    : 2 (server)
         - start_time              : 1686234849528674467
         - end_time                : 1686234849528756453
         - dropped_attributes_count: 0
         - dropped_events_count    : 0
         - status:
             - code        : 0
         - attributes:
             - http.method: 'GET'
             - http.scheme: 'http'
             - http.flavor: '1.1'
             - net.host.name: '172.17.0.2'
             - net.host.port: 8082
             - net.sock.peer.addr: '172.17.0.2'
             - net.sock.peer.port: 55952
             - http.user_agent: 'Wget/1.21.3'
             - http.wrote_bytes: 13
             - http.status_code: 200
         - events: none
         - [links]

Thanks!

[srini38]

@leonardo-albertovich leonardo-albertovich Looks like the processor_attributes plugin is intended to work with ctraces. Please let us know if this can be used to filter and exclude traces from service.name: 'hello-app' from being exported? Can processor_attributes plugin be used as of today?