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/azure-monitor/app/sdk-connection-string.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -59,10 +59,10 @@ A connection string consists of a list of settings represented as key-value pair
59
59
#### Syntax
60
60
61
61
-`InstrumentationKey` (for example, 00000000-0000-0000-0000-000000000000).
62
-
This is a *required* field.
62
+
`InstrumentationKey` is a *required* field.
63
63
-`Authorization` (for example, ikey). This setting is optional because today we only support ikey authorization.
64
64
-`EndpointSuffix` (for example, applicationinsights.azure.cn).
65
-
Setting the endpoint suffix will instruct the SDK on which Azure cloud to connect to. The SDK will assemble the rest of the endpoint for individual services.
65
+
Setting the endpoint suffix tells the SDK which Azure cloud to connect to. The SDK assembles the rest of the endpoint for individual services.
66
66
- Explicit endpoints.
67
67
Any service can be explicitly overridden in the connection string:
68
68
-`IngestionEndpoint` (for example, `https://dc.applicationinsights.azure.com`)
@@ -105,7 +105,7 @@ Here are some examples of connection strings.
In this example, the connection string specifies explicit overrides for every service. The SDK will use the exact endpoints provided without modification:
122
+
In this example, the connection string specifies explicit overrides for every service. The SDK uses the exact endpoints provided without modification:
0 commit comments