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
* adds changes to client pipeline and readme sample
* fixed padding and improved ReadMe sample
* moved headers to cosmos_headers, lowercased values
* changes for fully working diagnostics
* Update README.md
* use latest azcore version
* Update README.md
* Update cosmos_client_test.go
Copy file name to clipboardExpand all lines: sdk/data/azcosmos/README.md
+27Lines changed: 27 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -34,6 +34,33 @@ You can create an Azure Cosmos account using:
34
34
35
35
In order to interact with the Azure Cosmos DB service you'll need to create an instance of the Cosmos client class. To make this possible you will need an URL and key of the Azure Cosmos DB service.
36
36
37
+
#### Logging
38
+
39
+
The SDK can make use of `azcore`'s logging implementation to collect useful information for debugging your application. In order to make use of logs, one must set the environment variable `"AZURE_SDK_GO_LOGGING"` to `"all"` like outlined in this [public document](https://pkg.go.dev/github.com/Azure/azure-sdk-for-go/sdk/azcore#hdr-Built_in_Logging).
40
+
41
+
Once that is done, the SDK will begin to collect diagnostics. By default, it will output the logs to `stdout` - printing directly to your console - and will record all types of events (requests, responses, retries). If you'd like to configure a listener that acts differently, the small snippet below shows how you could do so.
0 commit comments