Implement activity_succeed_endtoend_latency and local_activity_succeed_endtoend_latency metrics #800
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
…d_endtoend_latency Issue temporalio#799
Spikhalskiy
requested review from
Sushisource,
mfateev and
vitarb
as code owners
Sushisource
approved these changes
Oct 6, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
What was changed
The misleading metric
activity_endtoend_latencyis replaced withactivity_succeed_endtoend_latencyand newlocal_activity_succeed_endtoend_latencywhich includes a latency between an activity schedule timestamp to the finish of successful completion of this activity.Closes #799