Flush deadlines and forwarder metadata #258
Draft
+288
−145
Conversation
This file contains hidden or 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
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.
Flush deadline
Add a deadline to the flush requests initiated by external users like the lambda-extension and future lambda-forwarder. This allows the flusher to specify a maximum time to wait for all messages to be flushed from the pipeline. The default is still to wait for a configured time based on the exporter.
Add metadata to logs_rx
Update the logs_rx channel, used by the lambda-exporter and lambda-forwarder to publish logs, to include Metadata by switching to the Message type.
Forwarder metadata
Expands the payload metadata support to include a new ForwarderMetadata. This will be used by the lambda-forwarder to ensure that each message is exported before reporting success back to the lambda API. It will only track a single request at a time, so it only tracks a request id.