Diagnostics: Adds DurationInMs to StoreResult#4462
Merged
microsoft-github-policy-service[bot] merged 11 commits intomasterfrom May 9, 2024
Merged
Diagnostics: Adds DurationInMs to StoreResult#4462microsoft-github-policy-service[bot] merged 11 commits intomasterfrom
microsoft-github-policy-service[bot] merged 11 commits intomasterfrom
Conversation
Member
How can this be used? Is the Start Time captured before the Task is created or after? If it's before, should this then be compared with the Create on the request timeline? |
ealsur
reviewed
Apr 30, 2024
Microsoft.Azure.Cosmos/src/Tracing/TraceWriter.TraceJsonWriter.cs
Outdated
Show resolved
Hide resolved
ealsur
reviewed
Apr 30, 2024
added 2 commits
April 30, 2024 21:20
Contributor
Author
The start time gets set before the task is created. I updated the description. |
ealsur
previously approved these changes
May 1, 2024
Member
ealsur
left a comment
There was a problem hiding this comment.
LGTM. Please add an example on the Description of how one would use the StartTime vs other info (Created?) to determine lag in Task execution.
@kirankumarkolli FYI
kirankumarkolli
approved these changes
May 8, 2024
ealsur
approved these changes
May 9, 2024
This was referenced Jul 28, 2025
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
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.
Pull Request Template
Description
This PR adds the store result duration time to the diagnostics. The information was already being captured but was not added to the JSON diagnostics. This is useful to help determine how long each individual request to the backend took and the duration between each call.
Example of a strong write. This shows the initial write is response time is 2024-05-01T16:01:48.4597873Z. The barrier request response time is 2024-05-01T16:01:48.6634187Z. This gives 204ms between response time and the barrier request took 86ms leaving 172ms between the write response and the start of the barrier request. Before the diagnostics only had the transport start time so it was not clear where the latency was coming from.
Type of change
Please delete options that are not relevant.
Closing issues
To automatically close an issue: closes #IssueNumber