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/correlation.md
+5-3Lines changed: 5 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,7 +13,7 @@ ms.reviewer: sergkanz
13
13
14
14
# Telemetry correlation in Application Insights
15
15
16
-
In the world of microservices, every logical operation requires work to be done in various components of the service. Each of these components can be monitored separately by [Azure Application Insights](../../azure-monitor/app/app-insights-overview.md). The web-app component communicates with the authentication provider component to validate user credentials, and with the API component to get data for visualization. The API component can query data from other services and use cache-provider components to notify the billing component about this call. Application Insights supports distributed telemetry correlation, which you use to detect which component is responsible for failures or performance degradation.
16
+
In the world of microservices, every logical operation requires work to be done in various components of the service. Each of these components can be monitored separately by [Azure Application Insights](../../azure-monitor/app/app-insights-overview.md). Application Insights supports distributed telemetry correlation, which you use to detect which component is responsible for failures or performance degradation.
17
17
18
18
This article explains the data model used by Application Insights to correlate telemetry sent by multiple components. It covers context-propagation techniques and protocols. It also covers the implementation of correlation concepts on different languages and platforms.
19
19
@@ -217,7 +217,7 @@ OpenCensus Python follows the `OpenTracing` data model specifications outlined a
217
217
218
218
### Incoming request correlation
219
219
220
-
OpenCensus Python correlates W3C Trace Context headers from incoming requests to the spans that are generated from the requests themselves. OpenCensus will do this automatically with integrations for popular web application frameworks such as `flask`, `django` and `pyramid`. The W3C Trace Context headers simply need to be populated with the [correct format](https://www.w3.org/TR/trace-context/#trace-context-http-headers-format)and sent with the request. Below is an example `flask` application demonstrating this.
220
+
OpenCensus Python correlates W3C Trace Context headers from incoming requests to the spans that are generated from the requests themselves. OpenCensus will do this automatically with integrations for the following popular web application frameworks: `flask`, `django` and `pyramid`. The W3C Trace Context headers simply need to be populated with the [correct format](https://www.w3.org/TR/trace-context/#trace-context-http-headers-format)and sent with the request. Below is an example `flask` application demonstrating this.
221
221
222
222
```python
223
223
from flask import Flask
@@ -250,7 +250,7 @@ Looking at the [Trace Context Header Format](https://www.w3.org/TR/trace-context
250
250
`parent-id/span-id`: `00f067aa0ba902b7`
251
251
`trace-flags`: `01`
252
252
253
-
If we take a look at the request entry that was sent to Azure Monitor, we can see fields populated with the trace header information.
253
+
If we take a look at the request entry that was sent to Azure Monitor, we can see fields populated with the trace header information. You can find this data under Logs(Analytics) in Azure Monitor Application Insights resource.
254
254
255
255

256
256
@@ -288,6 +288,8 @@ When this code is run, we get the following in the console:
288
288
```
289
289
Observe how there is a spanId present for the log message that is within the span, which is the same spanId that belongs to the span named `hello`.
290
290
291
+
You can export the log data using the `AzureLogHandler`. More information can be found [here](https://docs.microsoft.com/azure/azure-monitor/app/opencensus-python#logs)
292
+
291
293
## Telemetry correlation in .NET
292
294
293
295
Over time, .NET defined several ways to correlate telemetry and diagnostics logs:
0 commit comments