-
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 additional information #2570
Comments
What is the difference between TotalServiceProcessingTimeInMs and TotalNetworkingTimeInMs. If we all feel like that this information is essential then we can discuss about adding this information in telemetry also. |
TotalServiceProcessingTimeInMs is the time it took for Cosmos DB backend to process the request. It does not include any networking time like how long it was in the queue waiting to be processed. It's essentially RntbdRequestStats.TransitTime - response.BELatencyInMs TotalNetworkingTime is the time from when the SDK put the request on the wire and until it got a response. |
Adding a summary would greatly simplify the areas where customer can laser-focus on. |
How about include the wait-times? (concurrency forced waiting times) |
@kirankumarkolli can you expand on what you mean by concurrency forced waiting times? |
@asketagarwal what else is pending? |
The current diagnostics can have a lot of pages. This issue is to describe adding a summary to the top the diagnostics to make it easier to root cause.
Example of suggestion:
The text was updated successfully, but these errors were encountered: