Measure time performance App Service in Azure

Question

Measure time performance App Service in Azure

Francisco Capllonch Alcover 21

I'm trying to measure the performance time of an App Service that accesses to a CosmosDb database in our Azure environment.
I can not figure out what the gap in time that appears in the end-to-end transaction in AppInsights means, since the "Query documents" transaction against Cosmos Db finishes and the request "GET Documents/Search" ends.

0 comments

Answer accepted by question author

0 additional answers

Your answer

Answer 1

AnuragSingh-MSFT 21,566 Moderator

Hi @Francisco Capllonch Alcover ,

Thank you for reaching out to Microsoft Q&A for this question. I am sorry for the delayed response.

The timeline marked in the question denotes the time when "Query documents" step was not running. Based on the screenshot, that time period is after the CosmosDB has already responded. Only the shaded (blue region) region denotes the time period when "Query documents" step was being executed, i.e., it would be the time when CosmosDB was contacted and it responded with the result.

Please let me know if you have any questions.

---
Please 'Accept as answer' if it helped so that it can help others in the community looking for help on similar topics.

Francisco Capllonch Alcover 21 Reputation points

2022-12-20T07:02:41.97+00:00

Hi AnuragSigh!
From your response, the unknown time I'm trying to figure out what it refers is: " the time when CosmosDB was contacted and it responded with the result.". In that case, there is some problem with the CosmosDB because it's slowly responding.
Do you know how can I improve the CosmosDb response time?
AnuragSingh-MSFT 21,566 Reputation points Moderator

2022-12-20T08:26:32.587+00:00

@Francisco Capllonch Alcover , No, I am not saying that the region highlighted by you (using red line) is when Application was waiting on CosmosDB to respond back. I meant the blue colored region is when Application was waiting on CosmosDB to respond back (which is for 18ms). The following image should help clarify it

Please let me know if you have any questions.

---
Please 'Accept as answer' if it helped so that it can help others in the community looking for help on similar topics.
Francisco Capllonch Alcover 21 Reputation points

2022-12-20T08:59:04.56+00:00
So, the period of time I was refering to (red line) is source code time that can be both before or after execution of the call against CosmosDb . Something like this:

Source code before call to CosmosDb (red line time) .. Query documents Call to CosmosDb (blue colored region time) .. Source code after call to CosmosDb (red line time)
AnuragSingh-MSFT 21,566 Reputation points Moderator

2022-12-20T11:13:23.133+00:00

@Francisco Capllonch Alcover , thank you for the reply.
The shading of area (blue colored) is relative to timestamp. Therefore, the area that you highlighted (red color) are after the call to cosmosDB. Based on the screenshot shared, the following sequence happened

Start "GET Documents/Search" (at 0)
Call into "POST /oauth2/token" (which took 52 ms)
Call into "GET /idp/userinfo" (28 ms)
Call "Query documents" (18 ms)
Continue further in "GET Documents/Search"

Hope this helps. Please let me know if you have any questions.

---
Please 'Accept as answer' if it helped so that it can help others in the community looking for help on similar topics.

Share via

Measure time performance App Service in Azure

0 additional answers

Your answer