OpenTelemetry output plugin #12331
Unanswered
BaptisteMeynier
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hello everybody,
I use Fluentbit to redirect my Otel Data (trace, metric, log), for this I use OpenTelemetry output.
I have something like:
pipeline: outputs: - name: opentelemetry match: "*" host: otel-collector port: 4317 grpc: onI need to enriched with some metadata on each scope (trace, metric,log), so I use processor with opentelemetry-envelope but also add_label.
`
pipeline:
outputs:
- name: opentelemetry
match: "*"
host: otel-collector
port: 4317
grpc: on
add_label: service_name my-service
processors:
logs:
- name: opentelemetry_envelope
`
So, data for logs and metrics are identic excepted underscore (opentelemetry-collector-contrib allow automatic convertion).
Do you know if this is possible to factorise this for all Otel scope ?
I find processor usage in this case quite heavy. Do you think that It should be good to create new keys inspired by add_label usage ?
Something like a key for each Opentelemetry context resource_attributes, otel_scope_name, etc (context from content modifier)
All reactions