-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
[cmd/opampsupervisor] Report mismatched identifying attributes found during bootstrapping #29864
Comments
Pinging code owners for cmd/opampsupervisor: @evan-bradley @atoulme @tigrannajaryan. See Adding Labels via Comments if you do not have permissions to add labels yourself. |
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. |
This issue has been closed as inactive because it has been stale for 120 days with no activity. |
There's an associated TODO for this in the Supervisor code, and it is a case we should handle. |
@evan-bradley I can look into creating a PR for this |
I have created a rough PR for now: #37541 Regarding the report to the opamp server, we have a bit of a chicken-egg problem here, as the |
Component(s)
cmd/opampsupervisor
Is your feature request related to a problem? Please describe.
During bootstrapping, it may happen that the Supervisor's OpAMP server receives an AgentDescription message with a service instance ID or other identifying attribute that doesn't match what the Supervisor has set or expects.
This is a problem because the identifying attributes are intended to be used by the OpAMP server to determine which configuration to send to a Collector.
This could happen for a handful of reasons, using the instance ID as an example:
Describe the solution you'd like
If this happens, we should report the mismatch to the OpAMP server and stop the Collector. This behavior should be defined in the Supervisor specification document as well.
It's unclear whether the Supervisor should stay running after such an error occurs.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: