CosmosDB - Diagnostics in dotnet v3 SDK

Question

CosmosDB - Diagnostics in dotnet v3 SDK

banto 0

Hello,

We are using CosmosDB dotnet v3 SDK and we are fetching around 550kb of data in one query.

Here is a gist of the code:

User's image

We noticed that the “ReadNextAsync()” method takes 180ms to execute. After closer examinations of the diagnostics, we can see that 160ms is spent just by sending telemetry data to azure :

User's image

Is it possible to disable or control the sending of these telemetry statistics in the client application ?

Sai Raghunadh M 2,880 Reputation points Microsoft External Staff

2025-03-03T00:26:57.6066667+00:00

Hi @ banto

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
Oury Ba-MSFT 20,446 Reputation points Microsoft Employee

2025-03-06T18:24:37.4333333+00:00

@banto Thank you for reaching out.

Times are cumulative of the clients combined.

Further down in diagnostics the query call itself took ~166ms, is where the real time is spent.
Oury Ba-MSFT 20,446 Reputation points Microsoft Employee

2025-03-12T17:36:42.0233333+00:00

@banto

Please do let me know if you have additional queries or need further assistance.

1 answer

Your answer

Sai Raghunadh M 2,880 Reputation points Microsoft External Staff

2025-03-03T00:26:57.6066667+00:00

Hi @ banto

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
Oury Ba-MSFT 20,446 Reputation points Microsoft Employee

2025-03-06T18:24:37.4333333+00:00

@banto Thank you for reaching out.

Times are cumulative of the clients combined.

Further down in diagnostics the query call itself took ~166ms, is where the real time is spent.
Oury Ba-MSFT 20,446 Reputation points Microsoft Employee

2025-03-12T17:36:42.0233333+00:00

@banto

Please do let me know if you have additional queries or need further assistance.

Answer 1

Sai Raghunadh M 2,880 Microsoft External Staff

Hi @ banto

Thanks for the Question and using Microsoft @&A.

Yes, it is possible to disable or control the sending of telemetry statistics in a client application. The specific method depends on the application and the telemetry service being used. Here are a few general approaches:

If you're using Azure Application Insights, you can disable telemetry by setting the DisableTelemetry property to true in the TelemetryConfiguration object. This prevents any telemetry data from being sent.

https://dev.to/marktinderholt/mocking-telemetryclient-in-application-insights-a-simple-workaround-2mec

You can use telemetry initializers to filter out specific telemetry data. For example, you can create a telemetry initializer that ignores certain types of telemetry based on conditions

https://stackoverflow.com/questions/59535524/disable-application-insights-browser-telemetry-for-a-recurring-javascript-call

Hope this helps. Do let us know if you any further queries.

Sai Raghunadh M 2,880 Reputation points Microsoft External Staff

2025-03-04T01:16:20.3233333+00:00

Hi @ banto

Following up to see if the above answer was helpful. If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.
banto 0 Reputation points

2025-03-06T11:14:35.7066667+00:00

Hi, thanks for the answer.

No, we do not use AppInsight in Client code. I mean, we use the SDK in its default configuration. So how can we get rid or control the amount of analytics generated?
banto 0 Reputation points

2025-03-06T11:15:17.15+00:00

Hi, thanks for the answer.

No, we do not use AppInsight in Client code. I mean, we use the SDK in its default configuration. So how can we get rid or control the amount of analytics generated?
Vijayalaxmi Kattimani 1,720 Reputation points Microsoft External Staff

2025-03-06T14:16:58.59+00:00
Hi banto,

We apologize for the inconvenience caused.

We would like to inform you that, it is possible to disable or control the sending of telemetry statistics in the CosmosDB dotnet v3 SDK. You can achieve this by configuring the CosmosClientTelemetryOptions class. Specifically, you can set the DisableSendingMetricsToService property to true to disable sending telemetry data to Microsoft.

Here is an example of how you can do this:

CosmosClientOptions clientOptions = new CosmosClientOptions { CosmosClientTelemetryOptions = new CosmosClientTelemetryOptions { DisableSendingMetricsToService = true } }; CosmosClient cosmosClient = new CosmosClient("your-endpoint", "your-key", clientOptions);

This configuration will prevent the client application from sending telemetry data to Azure, which should help reduce the execution time of the ReadNextAsync() method.

Please refer to the below mentioned links for more information.

https://learn.microsoft.com/en-us/azure/cosmos-db/nosql/sdk-observability?tabs=dotnet

https://learn.microsoft.com/en-us/dotnet/api/microsoft.azure.cosmos.cosmosclienttelemetryoptions?view=azure-dotnet

https://github.com/Azure/azure-cosmos-dotnet-v3/blob/master/Microsoft.Azure.Cosmos/src/CosmosClientTelemetryOptions.cs

I hope this information helps. If the issue still persists, please let us know here. We will respond with more details and try to help you.
banto 0 Reputation points

2025-03-06T16:12:45.9766667+00:00

Hi, thanks for the answer.

We have tried all settings in the doc to try to disable it. Nevertheless we see no outcome in the sense that the Diagnostic part is still there:{

"Summary": {

"DirectCalls": {

"(200, 0)": 1

}

},

"name": "Typed FeedIterator ReadNextAsync",

"start datetime": "2025-03-06T16:07:57.211Z",

"duration in milliseconds": 154.5253,

"data": {

"Client Configuration": {

"Client Created Time Utc": "2025-03-06T16:07:25.2262627Z",

"MachineId": "hashedMachineName:328bf82f-9190-3277-09bb-902bd328b41e",

"NumberOfClientsCreated": 2,

"NumberOfActiveClients": 2,

"ConnectionMode": "Direct",

"User Agent": "cosmos-netstandard-sdk/3.47.2|2|X64|Microsoft Windows 10.0.22621|.NET 8.0.12|N|",

"ConnectionConfig": {

"gw": "(cps:50, urto:6, p:False, httpf: False)",

"rntbd": "(cto: 5, icto: -1, mrpc: 30, mcpe: 65535, erd: True, pr: ReuseUnicastPort)",

"other": "(ed:False, be:False)"

},

"ConsistencyConfig": "(consistency: NotSet, prgns:[], apprgn: )",

"ProcessorCount": 8

},

"Query Correlated ActivityId": "ab1f5242-148d-4c61-87f9-a5efb5c7023c"

},

"children": [

{

"name": "Create Query Pipeline",

"duration in milliseconds": 0.5506,

"children": [

{

"name": "Get Container Properties",

"duration in milliseconds": 0.0167,

"children": [

{

"name": "Get Collection Cache",

"duration in milliseconds": 0.0018

}

]

},

{

"name": "Service Interop Query Plan",

"duration in milliseconds": 0.4108

},

{

"name": "Get Partition Key Ranges",

"duration in milliseconds": 0.0616,

"children": [

{

"name": "Try Get Overlapping Ranges",

"duration in milliseconds": 0.0344

}

]

}

]

},

{

"name": "MoveNextAsync",

"duration in milliseconds": 134.2758,

"children": [

{

"name": "[,FF) move next",

"duration in milliseconds": 134.2486,

"children": [

{

"name": "Prefetch",

"duration in milliseconds": 134.2398,

"children": [

{

"name": "[,FF) move next",

"duration in milliseconds": 134.215,

"data": {

.....

},

"children": [

{

"name": "Microsoft.Azure.Cosmos.Handlers.RequestInvokerHandler",

"duration in milliseconds": 134.0625,

"children": [

{

"name": "Get Collection Cache",

"duration in milliseconds": 0.0008

},

{

"name": "Get Partition Key Range Cache",

"duration in milliseconds": 0.0003

},

{

"name": "Try Get Overlapping Ranges",

"duration in milliseconds": 0.0068

},

{

"name": "Microsoft.Azure.Cosmos.Handlers.DiagnosticsHandler",

"duration in milliseconds": 133.9785,

....
banto 0 Reputation points

2025-03-06T16:14:12.8033333+00:00

Thanks for the answer. We have tried all possible config in the doc to disable diagnostics. But we still see them being generated:

{

"Summary": {

"DirectCalls": {

"(200, 0)": 1

}

},

"name": "Typed FeedIterator ReadNextAsync",

"start datetime": "2025-03-06T16:07:57.211Z",

"duration in milliseconds": 154.5253,

"data": {

"Client Configuration": {

"Client Created Time Utc": "2025-03-06T16:07:25.2262627Z",

"MachineId": "hashedMachineName:328bf82f-9190-3277-09bb-902bd328b41e",

"NumberOfClientsCreated": 2,

"NumberOfActiveClients": 2,

"ConnectionMode": "Direct",

"User Agent": "cosmos-netstandard-sdk/3.47.2|2|X64|Microsoft Windows 10.0.22621|.NET 8.0.12|N|",

"ConnectionConfig": {

"gw": "(cps:50, urto:6, p:False, httpf: False)",

"rntbd": "(cto: 5, icto: -1, mrpc: 30, mcpe: 65535, erd: True, pr: ReuseUnicastPort)",

"other": "(ed:False, be:False)"

},

"ConsistencyConfig": "(consistency: NotSet, prgns:[], apprgn: )",

"ProcessorCount": 8

},

"Query Correlated ActivityId": "ab1f5242-148d-4c61-87f9-a5efb5c7023c"

},

"children": [

{

"name": "Create Query Pipeline",

"duration in milliseconds": 0.5506,

"children": [

{

"name": "Get Container Properties",

"duration in milliseconds": 0.0167,

"children": [

{

"name": "Get Collection Cache",

"duration in milliseconds": 0.0018

}

]

},

{

"name": "Service Interop Query Plan",

"duration in milliseconds": 0.4108

},

{

"name": "Get Partition Key Ranges",

"duration in milliseconds": 0.0616,

"children": [

{

"name": "Try Get Overlapping Ranges",

"duration in milliseconds": 0.0344

}

]

}

]

},

{

"name": "MoveNextAsync",

"duration in milliseconds": 134.2758,

"children": [

{

"name": "[,FF) move next",

"duration in milliseconds": 134.2486,

"children": [

{

"name": "Prefetch",

"duration in milliseconds": 134.2398,

"children": [

{

"name": "[,FF) move next",

"duration in milliseconds": 134.215,

"data": {

"Query Metrics": "Retrieved Document Count : 10 \r\nRetrieved Document Size : 307,343 bytes \r\nOutput Document Count : 10 \r\nOutput Document Size : 285,076 bytes \r\nIndex Utilization : 100.00 % \r\nTotal Query Execution Time : 3.19 milliseconds\r\n Query Preparation Time : 0.20 milliseconds\r\n Index Lookup Time : 0.25 milliseconds\r\n Document Load Time : 0.20 milliseconds\r\n Runtime Execution Times : 0.01 milliseconds\r\n Document Write Time : 2.10 milliseconds\r\n\r\nIndex Utilization Information\r\n Utilized Single Indexes\r\n Potential Single Indexes\r\n Utilized Composite Indexes\r\n Potential Composite Indexes\r\n"

},

"children": [

{

"name": "Microsoft.Azure.Cosmos.Handlers.RequestInvokerHandler",

"duration in milliseconds": 134.0625,

"children": [

{

"name": "Get Collection Cache",

"duration in milliseconds": 0.0008

},

{

"name": "Get Partition Key Range Cache",

"duration in milliseconds": 0.0003

},

{

"name": "Try Get Overlapping Ranges",

"duration in milliseconds": 0.0068

},

{

"name": "Microsoft.Azure.Cosmos.Handlers.DiagnosticsHandler",

"duration in milliseconds": 133.9785,

Share via

CosmosDB - Diagnostics in dotnet v3 SDK

1 answer

Your answer