fix(inputs.kinesis_consumer): Store iterator of last delivered message, not first #16304
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.
Summary
When storing shard iterators in DynamoDB the current code stores the iterator of the first metric delivered in the current
interval
to the outputs. This is sub-optimal if many messages delivered in a bulk and telegraf is exited before the next gather cycle.This PR fixes the issue by storing the iterator of the last metric delivered.
Checklist
Related issues