fix formatting on concepts.md (#1868)
This commit is contained in:
Родитель
d1865fcba9
Коммит
d3319662bf
|
@ -1,13 +1,10 @@
|
|||
# Application Insights DotNet SDK Concepts
|
||||
This lists the high level concepts of the AI DotNet SDK and links to detailed guides to help you get started.
|
||||
|
||||
|
||||
To use the Application Insights SDK you must configure an Instrumentation Key which can be [obtained from an Application Insights resource](https://docs.microsoft.com/azure/azure-monitor/app/create-new-resource).
|
||||
Or you can use a [Connection string](https://docs.microsoft.com/azure/azure-monitor/app/sdk-connection-string?tabs=net) to simplify the configuration of our endpoints.
|
||||
Both an Instrumentation Key and Connection String are provided for you on the Overivew Dashboard of your Application Insights resource.
|
||||
|
||||
|
||||
|
||||
## TelemetryClient
|
||||
The `TelemetryClient` object is the primary root object for the library.
|
||||
Almost all functionality around telemetry sending is located on this object.
|
||||
|
@ -54,8 +51,6 @@ catch(Exception ex)
|
|||
}
|
||||
```
|
||||
|
||||
|
||||
|
||||
## Telemetry Channels
|
||||
Telemetry channels are responsible for sending the telemetry data to the designated place. Optional features can be provided by the telemetry channels, for example, buffering the data and sending in them in batches, persisting the data to a local storage in case of transmission failure (e.g. network outage), traffic shaping and retry mechanisms
|
||||
|
||||
|
@ -65,30 +60,22 @@ The .NET and .NET Core versions of the SDKs provide two built-in telemetry chann
|
|||
|
||||
Please review our full guide on [Telemetry Channels in Application Insights](https://docs.microsoft.com/azure/azure-monitor/app/telemetry-channels).
|
||||
|
||||
|
||||
|
||||
## TelemetryProcessors and TelemetryInitializers
|
||||
You can write and configure plug-ins for the Application Insights SDK to customize how telemetry can be enriched and processed before it's sent to the Application Insights service.
|
||||
|
||||
Please review our full guide on [Filtering and preprocessing telemetry](https://docs.microsoft.com/azure/azure-monitor/app/api-filtering-sampling).
|
||||
|
||||
|
||||
|
||||
## Telemetry correlation
|
||||
Application Insights supports distributed telemetry correlation, which you use to detect which component is responsible for failures or performance degradation.
|
||||
|
||||
Please review our full guide on [Telemetry correlation in Application Insights](https://docs.microsoft.com/azure/azure-monitor/app/correlation).
|
||||
|
||||
|
||||
|
||||
## Custom metric collection
|
||||
The Azure Monitor Application Insights .NET and .NET Core SDKs have two different methods of collecting custom metrics, `TrackMetric()`, and `GetMetric()`. The key difference between these two methods is local aggregation.
|
||||
|
||||
Please review our full guide on [Custom metric collection in .NET and .NET Core](https://docs.microsoft.com/azure/azure-monitor/app/get-metric).
|
||||
|
||||
|
||||
|
||||
### Sampling
|
||||
## Sampling
|
||||
Sampling is the recommended way to reduce telemetry traffic, data costs, and storage costs, while preserving a statistically correct analysis of application data.
|
||||
|
||||
Please review our full guide on [Sampling in Application Insights](https://docs.microsoft.com/azure/azure-monitor/app/sampling).
|
||||
|
|
Загрузка…
Ссылка в новой задаче