Add checkin_pid to CheckinObserved #106
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
fearful-symmetry
requested review from
michalpristas and
pchila
and removed request for
a team
cmacknz
reviewed
Mar 26, 2024
cmacknz
approved these changes
Mar 26, 2024
💚 Build Succeeded
History
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Continuation of elastic/elastic-agent#4083
In order to get elastic-agent to monitor endpoint, we need to know the pid of endpoint, which we currently can't do, as Endpoint operates a bit more independently than the other beats that are talking to agent. Endpoint can restart independently, and Agent can't track the PID on its own.
This adds a
checkin_pidinteger toCheckinObserved. I put it here for two reason:CheckinObservedseems like the most logical place to put a new PID.