Skip to content
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

Discovery observers Start failures should not stop nor crash the collector #5299

Merged

Conversation

pjanotti
Copy link
Contributor

@pjanotti pjanotti commented Aug 30, 2024

In #5202 the discovery code was changed so the collector ended its start up in case any observer failed to start - this behavior was agreed per conversation. However, the docker observer had a behavior that if it failed to start on mac and Linux it didn't crash as in Windows. This cemented a behavior on the collector that was changed by #5202: the collector started successfully even if the docker observer failed. This change restores the previous behavior while not adding the risk of crashing in observers that failed to start (that's why it is not a simple reverse).

In the future we may want to consider if having a strict discovery mode is desirable. In this mode the user could enter an option to indicate that discovery should fail if any observer or receiver fails to be created or started.

@pjanotti pjanotti marked this pull request as ready for review August 30, 2024 03:46
@pjanotti pjanotti requested review from a team as code owners August 30, 2024 03:46
@pjanotti pjanotti merged commit c819395 into signalfx:main Aug 30, 2024
240 of 241 checks passed
@pjanotti pjanotti deleted the discovery-failures-do-not-stop-the-collector branch August 30, 2024 17:06
@github-actions github-actions bot locked and limited conversation to collaborators Aug 30, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants