feat: Add entity_guid to Agent Control health file
#3594
+224
−3
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.
Description
To facilitate establishing relationships between fleet control agent entities and the related APM service that an agent creates, the entity guid will now be part of the health file written out for agent control. Note that this new field MUST be the first entry in the health file.
From the spec:
"| entity_guid | string | The primary entity GUID received in the connect response. This MUST be the first field in the health file |
This format is based on the OpAMP protocol. The entity
GUID is the first field in the file so as not to break the OpAmp compatibility in the remainder of the file.
For a health file written out prior to the entity GUID being available, the agent should include the
entity_guidkey with an empty value."How to Test
Related Issues
Closes #3591