-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[opampsupervisor] don't merge multiple received agent config files #34608
Comments
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
We had discussed this in the past, and I think we agreed this would be the best way to do it -- we need open-telemetry/opentelemetry-collector#8754 to do this though, in order to support this type of merging (which we require for the opamp extension to be configured). |
Removing |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
Component(s)
cmd/opampsupervisor
Is your feature request related to a problem? Please describe.
Right now the supervisor merges the received config files meaning that pipeline names need to be unique in across all files the config-map. if this is not done the supervisor silently "deletes" config pipelines and no errors are thrown anywhere and proper execution can (and will) be assumed by the collector and the end-user.
Will result in this
effective.yaml
Describe the solution you'd like
Save each received AgentConfigFile as a seperate file and give each to the collector --config cli param as it support multiple files.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: