Conversation
42e12d9 to
14f556b
Compare
Signed-off-by: Bence Csati <bence.csati@axoflow.com>
Signed-off-by: Bence Csati <bence.csati@axoflow.com>
14f556b to
a2344e8
Compare
OverOrion
left a comment
There was a problem hiding this comment.
The problem you experienced is (mostly) solved with open-telemetry/opentelemetry-collector#12097
One we do a version upgrade we can opt into this if we want to. (Not applicable for processors though, that's why I said mostly.)
The bottom line is that we can keep common-config.yaml and all the specific yamls can specify their own whole logs pipeline for now:
receivers: [azureeventhub]
processors: [resource/axoflow, resourcedetection/system,, resource/axoflow_device_id]
exporters: [otlp/axorouter]The root cause is that list merging is not supported as of now, and it gets overwritten. However we can still leverage yaml merging capability by only duplication the logs pipeline part.
What do you think?
I believe that if this issue was present before, and now it would only be available under a feature-gate, I would go with not using a common-config, because I would like to avoid problems like these in the future. Also there is not that much we gain from a common-config, if you check the individual configs in this PR, I marked provider-specific configs with a comment, and that is not too much, we needed to add. In other words this does not pose a huge "maintain-burden" on us IMHO. |
Signed-off-by: Bence Csati <bence.csati@axoflow.com>
a2344e8 to
bdeaaff
Compare
No description provided.