enhancement: batch events out metric in Pipeline #8383
Merged
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.
Instead of incrementing
events_out_total
-- viaemit!(EventOut { .. })
-- every time we get an event inPipeline
, we instead batch the updates and flush them out inPipeline::try_flush
. For high events/second configurations, this can provide a significant reduction in metric emissions overall.Signed-off-by: Toby Lawrence [email protected]