What's the recommended processor ordering for OpenTelemetry Collector configuration #30810
Replies: 1 comment
-
Hey guys, I actually found the solution to my issue. In the documentation on k8sattributes processor it is stated that
And also in the documentation of tail sampling processor it is stated that
So that's where I found out why I was able to see Kubernetes related attributes when Hope this helps someone who is facing a similar issue. Thank you. |
Beta Was this translation helpful? Give feedback.
-
I'm configuring processors for the OpenTelemetry Collector, and I'm encountering some confusion regarding the recommended order of processors, and an issue particularly in relation to the
k8sattributes
processor.When I use the following order of processors in my configuration:
I'm not seeing the Kubernetes attributes in my traces.
However, when I switch the order to:
I do see the Kubernetes attributes in traces.
And when I look at the documentation here for the batch processor, it states:
Considering this recommendation, I'm unsure on what is making the k8sattributes processor to not work. Could someone clarify the issue or tell me when am I going wrong?
Also please let me know the recommended order of processors for the OpenTelemetry Collector configuration, particularly in relation to the batch processor and any other relevant considerations.
Thank you.
Implementation:
Initially, I configured the processors in the following order in my YAML configuration file:
In this configuration, I expected the OpenTelemetry Collector to include Kubernetes attributes in the traces it collects.
Expectation:
The Kubernetes attributes should be present in the collected traces.
Actual Result:
The Kubernetes attributes were not included in the traces.
Further Experimentation:
In an attempt to troubleshoot the issue, I rearranged the order of processors in the configuration file to the following:
I was able to successfully capture Kubernetes attributes in the traces.
Beta Was this translation helpful? Give feedback.
All reactions