feat(processor): Add a metric to track the time of all messages#2877
Merged
feat(processor): Add a metric to track the time of all messages#2877
Conversation
olksdr
approved these changes
Dec 20, 2023
Dav1dde
approved these changes
Dec 20, 2023
iker-barriocanal
approved these changes
Dec 20, 2023
jan-auer
added a commit
that referenced
this pull request
Dec 20, 2023
* master: feat(processor): Add a metric to track the time of all messages (#2877) build(py): Update to python 3.9 (#2876) fix(spans): Collapse constants in SQL select (#2867) fix(spans): Parse quotes in MySQL (#2846) ref(cardinality): Use a Lua script and in-memory cache for the cardinality limiter (#2849) fix(spans): Detect hex with fallback scrubber (#2868)
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
4 participants
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.
In order to estimate the throughput and capacity of the envelope
processor service, we're tracking the number and duration of all
processed messages. This should allow us to assess when the CPU pool is
reaching its limit.
The metric is tracked as
processor.message.durationand has amessagetag containing the name of the variant / struct that is beingprocessed. This allows to break down the volume and duration of each of
the messages by type.