Skip to content

Commit 357984c

Browse files
Merge branch 'update_azure_cosmos_java_capture_diagnostics' of github.com:kushagraThapar/azure-docs-pr into update_azure_cosmos_java_capture_diagnostics
2 parents bfde1b9 + 085a50a commit 357984c

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/cosmos-db/nosql/troubleshoot-java-sdk-v4.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -198,7 +198,7 @@ itemResponseMono.onErrorResume(throwable -> {
198198
---
199199

200200
## Logging the diagnostics
201-
Java V4 SDK versions v4.43.0 and above support automatic logging of Cosmos Diagnostics for all requests or errors if they meet certain criteria. Application developers can define thresholds for latency (for point or non-point operations), request charge and payload size. If the requests exceed these defined thresholds, the cosmos diagnostics for those requests will be emitted automatically.
201+
Java V4 SDK versions v4.43.0 and above support automatic logging of Cosmos Diagnostics for all requests or errors if they meet certain criteria. Application developers can define thresholds for latency (for point (create, read, replace, upsert, patch) or non-point operations (query, change feed, bulk and batch)), request charge and payload size. If the requests exceed these defined thresholds, the cosmos diagnostics for those requests will be emitted automatically.
202202

203203
By default, the Java v4 SDK logs these diagnostics automatically in a specific format. However, this can be changed by implementing `CosmosDiagnosticsHandler` interface and providing your own custom Diagnostics Handler.
204204

0 commit comments

Comments
 (0)