Is it possible to use processors from opentelemetry-collector-contrib? #6533
-
Hi everyone, Is there any way to get this to work? Sorry if this question was answered before, I searched for "contrib" and "processor" but couldn't find anything. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
Hey @niklasteichmann, I'm here to help you with any bugs, questions, or contributions you have. Let's dive in and figure this out together! Yes, it is possible to use processors from the For example, to include a processor like the Tail Sampling Processor, you would add it to your configuration like this: processors:
tailsampling:
decision_wait: 5s
num_traces: 10000
expected_new_traces_per_sec: 100
policies:
- name: test-policy
type: always_sample This setup can be adapted for other processors, such as the redaction processor, by following the specific configuration requirements for that processor [1][2]. To continue talking to Dosu, mention @dosu. Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other |
Beta Was this translation helpful? Give feedback.
-
It is only possible to use the components that are directly included in the Jaeger binary, which are enumerated in the docs https://www.jaegertracing.io/docs/2.2/architecture/#opentelemetry-components If you want to use any other contrib (or otherwise) components you should run an OTEL Collector in front of Jaeger, as OTEL Collector allows more flexibility in how to include plugins. |
Beta Was this translation helpful? Give feedback.
It is only possible to use the components that are directly included in the Jaeger binary, which are enumerated in the docs https://www.jaegertracing.io/docs/2.2/architecture/#opentelemetry-components
If you want to use any other contrib (or otherwise) components you should run an OTEL Collector in front of Jaeger, as OTEL Collector allows more flexibility in how to include plugins.