You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/cosmos-db/nosql/index-metrics.md
+40-1Lines changed: 40 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,7 +21,7 @@ Azure Cosmos DB provides indexing metrics to show both utilized indexed paths an
21
21
22
22
You can enable indexing metrics for a query by setting the `PopulateIndexMetrics` property to `true`. When not specified, `PopulateIndexMetrics` defaults to `false`. We only recommend enabling the index metrics for troubleshooting query performance. As long as your queries and indexing policy stay the same, the index metrics are unlikely to change. Instead, we recommend identifying expensive queries by monitoring query RU charge and latency using diagnostic logs.
23
23
24
-
### .NET SDK example
24
+
##[.NET SDK](#tab/dotnet)
25
25
26
26
```csharp
27
27
stringsqlQueryText="SELECT TOP 10 c.id FROM c WHERE c.Item = 'value1234' AND c.Price > 2";
@@ -43,6 +43,45 @@ You can enable indexing metrics for a query by setting the `PopulateIndexMetrics
43
43
}
44
44
```
45
45
46
+
## [Java SDK Sync](#tab/java-sync)
47
+
48
+
```java
49
+
SqlQuerySpec querySpec =newSqlQuerySpec("SELECT TOP 10 c.id FROM c WHERE c.Item = 'value1234' AND c.Price > 2");
0 commit comments