Skip to content
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

[Internal] Design Docs: Adds Design Document for Client Telemetry Part 2 #3903

Merged
3 commits merged into from
Jun 9, 2023
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions docs/observability.md
Original file line number Diff line number Diff line change
Expand Up @@ -39,19 +39,19 @@ flowchart TD

### Introduction
When opted-in CosmosDB SDK collects below aggregated telemetry data every 10 minutes to Azure CosmosDB service.
1. Operation(CRUD APIs) Latencies and Request Units (RUs).
1. Operation(Point, Stream, Batch and Query APIs) Latencies and Request Units (RUs).
2. Metadata caches (ex: CollectionCache) miss statistics
3. Client System Usage (during an operation) :
3. Host Resource Usage: (during an operation) :
* CPU usage
* Memory Usage
* Thread Starvation
* Network Connections Opened (only TCP Connections)
4. TOP 10 slower network interactions
4. TOP 10 slowest network interactions per endpoint

> Note: We don't collect any PII data as part of this feature.

### Benefits
Enabling this feature provides numerous benefits. The telemetry data collected will allow us to identify and address potential issues. This results in a superior support experience and ensures that some issues can even be resolved before they impact your application. In short, customers with this feature enabled can expect a smoother and more reliable experience.
Enabling this feature provides numerous benefits. The telemetry data collected will allow us to identify and address potential issues. This results in a superior support experience and ensures that some issues can even be resolved before they impact your application. In short, customers with this feature enabled can expect a smoother and more reliable support experience.

### Impact of this feature enabled
* _Latency_: Customer should not see any impact on latency.
Expand Down