-
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
[cmd/opampsupervisor] Forward custom messages to/from agent #33576
[cmd/opampsupervisor] Forward custom messages to/from agent #33576
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This generally looks good to me. I'd appreciate a review from @evan-bradley as well though.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry for the delay, this looks good to me. Thanks @djaglowski for taking a look.
@tigrannajaryan I'll leave this open in case you want to take a look, otherwise I'll merge this by Friday if I am able, or next Monday at the latest.
bb75b96
to
76a82ba
Compare
@tigrannajaryan Gentle bump on this, it's ready for re-review when you get a chance 😄 |
@BinaryFissionGames I am out this week, won't be able to review. Please feel free to merge, no need to wait for me. |
**Description:** Follow-up to #33576. Boolean short-circuiting was causing the `onMessage` handler to not process the whole `ServerToAgent` message if it included multiple fields. I noticed this was causing the Collector to fail to start when using the opamp-go demo server; the own metrics section is required for the Collector to start since it provides the only pipelines by default. I included a new unit test that verifies everything looks as we would expect when getting a message like what would be sent by the example server. --------- Co-authored-by: Evan Bradley <evan-bradley@users.noreply.github.com>
…telemetry#34349) **Description:** Follow-up to open-telemetry#33576. Boolean short-circuiting was causing the `onMessage` handler to not process the whole `ServerToAgent` message if it included multiple fields. I noticed this was causing the Collector to fail to start when using the opamp-go demo server; the own metrics section is required for the Collector to start since it provides the only pipelines by default. I included a new unit test that verifies everything looks as we would expect when getting a message like what would be sent by the example server. --------- Co-authored-by: Evan Bradley <evan-bradley@users.noreply.github.com>
Description:
Link to tracking Issue: Closes #33575
Testing: