-
Notifications
You must be signed in to change notification settings - Fork 494
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Diagnostics: Adds DurationInMs to StoreResult #4462
Diagnostics: Adds DurationInMs to StoreResult #4462
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All good!
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? |
Microsoft.Azure.Cosmos/src/Tracing/TraceWriter.TraceJsonWriter.cs
Outdated
Show resolved
Hide resolved
…azure-cosmos-dotnet-v3 into origin/j82w/startTimeDiag
The start time gets set before the task is created. I updated the description. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @j82w. Will help troubleshooting.
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