feat(gateway-engine-core): thread-safe batched non-blocking metrics consumer#2126
Merged
Conversation
A generic batched metrics consumer that should allow batched, thread-safe non-blocking metrics ingestion by many different metrics implementations, rather than reinventing this pattern many times. This implementation runs as fast as it can, using a spin-wait worker thread that polls a non-blocking queue. It passes these metrics to a call-handler which may then go and perform actions such as serializing and transmitting those metrics. This implementation does not have a minimum batch size nor minimum polling interval.
msavy
changed the title
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
1 participant
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.
A generic batched metrics consumer that should allow batched, thread-safe non-blocking metrics
ingestion by many different metrics implementations, rather than reinventing this pattern many
times.
This implementation runs as fast as it can, using a spin-wait worker thread that polls a
non-blocking queue. It passes these metrics to a call-handler which may then go and perform
actions such as serializing and transmitting those metrics.
This implementation does not have a minimum batch size nor minimum polling interval.