You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a follow up from #35135. The shipper event protocol defines a PersistedIndex API for end to end acknowledgement from the output back to the input. This is critically important to ensuring that the Filebeat registry will continue to function as designed when using the shipper.
Hi!
We just realized that we haven't looked into this issue in a while. We're sorry!
We're labeling this issue as Stale to make it hit our filters and make sure we get back to it as soon as possible. In the meantime, it'd be extremely helpful if you could take a look at it as well and confirm its relevance. A simple comment with a nice emoji will be enough :+1.
Thank you for your contribution!
This is a follow up from #35135. The shipper event protocol defines a
PersistedIndex
API for end to end acknowledgement from the output back to the input. This is critically important to ensuring that the Filebeat registry will continue to function as designed when using the shipper.The shipper PersistedIndex API is described in detail in https://github.com/elastic/elastic-agent-shipper-client/tree/main/api#publication-acknowledgements. Implement the PersistedIndex API in the Filebeat shipper input.
Acceptance Criteria
The text was updated successfully, but these errors were encountered: