-
Notifications
You must be signed in to change notification settings - Fork 2.8k
[cmd/opampsupervisor] chore: Store RemoteConfigStatus in persistent state #40467
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] chore: Store RemoteConfigStatus in persistent state #40467
Conversation
548570b
to
f492893
Compare
I see we pass the remote config status in the OpAMP client start settings. Is this reported right away without starting the Collector? |
Yep. This remote config status is reported as soon as the OpAMP client connects to the server. This is where it is defined in the OpAMP-Go code: https://github.com/open-telemetry/opamp-go/blob/main/client/types/startsettings.go#L35-L40 |
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.
Looks good to me. Thanks for the additional info.
Marking as draft for a bit. Found one edge case issue this should fix but doesn't. |
This is ready to go again. Found an edge case when getting sent an empty config we'd report an unhealthy status when we don't want to. Updated an e2e test to make sure it's healthy. |
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.
@evan-bradley can you take one last look after the latest change?
EDIT: I've marked this PR with do-not-merge
, @evan-bradley please take the label off and merge when you take a look.
cmd/opampsupervisor/Library/Caches/Snowflake/ocsp_response_cache.json
Outdated
Show resolved
Hide resolved
This is ready for another look. |
Description
Link to tracking issue
Fixes
Testing
Documentation