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/asp-net-core.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -168,12 +168,12 @@ Run your application and make requests to it. Telemetry should now flow to Appli
168
168
169
169
### Live metrics
170
170
171
-
[Live metrics](./live-stream.md) can be used to quickly verify if Application Insights monitoring is configured correctly. It might take a few minutes for telemetry to appear in the portal and analytics, but live metrics shows CPU usage of the running process in near real time. It can also show other telemetry like requests, dependencies, and traces.
171
+
[Live metrics](./live-stream.md) can be used to quickly verify if Application Insights monitoring is configured correctly. It might take a few minutes for telemetry to appear in the portal and analytics, but the live metrics pane shows CPU usage of the running process in near real time. It can also show other telemetry like requests, dependencies, and traces.
172
172
173
173
#### Enable live metrics by using code for any .NET application
174
174
175
175
> [!NOTE]
176
-
> Live metrics is enabled by default when you onboard it by using the recommended instructions for .NET applications.
176
+
> Live metrics are enabled by default when you onboard it by using the recommended instructions for .NET applications.
Copy file name to clipboardExpand all lines: articles/azure-monitor/app/asp-net.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -363,12 +363,12 @@ For the template-based ASP.NET MVC app from this article, the file that you need
363
363
364
364
## Live metrics
365
365
366
-
[Live metrics](./live-stream.md) can be used to quickly verify if Application Insights monitoring is configured correctly. It might take a few minutes for telemetry to appear in the portal and analytics, but live metrics shows CPU usage of the running process in near real time. It can also show other telemetry like requests, dependencies, and traces.
366
+
[Live metrics](./live-stream.md) can be used to quickly verify if Application Insights monitoring is configured correctly. It might take a few minutes for telemetry to appear in the portal and analytics, but the live metrics pane shows CPU usage of the running process in near real time. It can also show other telemetry like requests, dependencies, and traces.
367
367
368
368
### Enable live metrics by using code for any .NET application
369
369
370
370
> [!NOTE]
371
-
> Live metrics is enabled by default when you onboard it by using the recommended instructions for .NET applications.
371
+
> Live metrics are enabled by default when you onboard it by using the recommended instructions for .NET applications.
Copy file name to clipboardExpand all lines: articles/azure-monitor/app/live-stream.md
+17-17Lines changed: 17 additions & 17 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@ ms.devlang: csharp
9
9
10
10
# Live metrics: Monitor and diagnose with 1-second latency
11
11
12
-
Monitor your live, in-production web application by using live metrics (also known as QuickPulse) from [Application Insights](./app-insights-overview.md). You can select and filter metrics and performance counters to watch in real time, without any disturbance to your service. You can also inspect stack traces from sample failed requests and exceptions. Together with [Profiler](./profiler.md) and [Snapshot Debugger](./snapshot-debugger.md), live metrics provides a powerful and noninvasive diagnostic tool for your live website.
12
+
Monitor your live, in-production web application by using live metrics (also known as QuickPulse) from [Application Insights](./app-insights-overview.md). You can select and filter metrics and performance counters to watch in real time, without any disturbance to your service. You can also inspect stack traces from sample failed requests and exceptions. Together with [Profiler](./profiler.md) and [Snapshot Debugger](./snapshot-debugger.md), live metrics provide a powerful and noninvasive diagnostic tool for your live website.
13
13
14
14
> [!NOTE]
15
15
> Live metrics only supports TLS 1.2. For more information, see [Troubleshooting](#troubleshooting).
@@ -26,32 +26,32 @@ With live metrics, you can:
26
26
27
27
:::image type="content" source="./media/live-stream/live-metric.png" lightbox="./media/live-stream/live-metric.png" alt-text="Screenshot that shows the live metrics tab.":::
28
28
29
-
Live metrics is currently supported for ASP.NET, ASP.NET Core, Azure Functions, Java, and Node.js apps.
29
+
Live metrics are currently supported for ASP.NET, ASP.NET Core, Azure Functions, Java, and Node.js apps.
30
30
31
31
> [!NOTE]
32
-
> The number of monitored server instances displayed by live metrics might be lower than the actual number of instances allocated for the application. This mismatch is because many modern web servers will unload applications that don't receive requests over a period of time to conserve resources. Because live metrics only counts servers that are currently running the application, servers that have already unloaded the process won't be included in that total.
32
+
> The number of monitored server instances displayed by live metrics might be lower than the actual number of instances allocated for the application. This mismatch is because many modern web servers will unload applications that don't receive requests over a period of time to conserve resources. Because live metrics only count servers that are currently running the application, servers that have already unloaded the process won't be included in that total.
33
33
34
34
## Get started
35
35
36
36
> [!IMPORTANT]
37
-
> To enable Application Insights, ensure that it's activated in the Azure portal and your app is using a recent version of the [Azure Monitor OpenTelemetry Distro](opentelemetry-enable.md) or Classic [Application Insights](https://www.nuget.org/packages/Microsoft.ApplicationInsights.AspNetCore) NuGet package. Without the NuGet package, some telemetry is sent to Application Insights, but that telemetry won't show in live metrics.
37
+
> To enable Application Insights, ensure that it's activated in the Azure portal and your app is using a recent version of the [Azure Monitor OpenTelemetry Distro](opentelemetry-enable.md) or Classic [Application Insights](https://www.nuget.org/packages/Microsoft.ApplicationInsights.AspNetCore) NuGet package. Without the NuGet package, some telemetry is sent to Application Insights, but that telemetry won't show in the live metrics pane.
38
38
39
39
1. Follow language-specific guidelines to enable live metrics:
40
40
41
41
# [OpenTelemetry (Recommended)](#tab/otel)
42
42
43
-
*[ASP.NET](opentelemetry-enable.md?tabs=net): Live metrics *is not supported*.
44
-
*[ASP.NET Core](opentelemetry-enable.md?tabs=aspnetcore): Live metrics is enabled by default.
45
-
*[Java](./opentelemetry-enable.md?tabs=java): Live metrics is enabled by default.
46
-
*[Node.js](opentelemetry-enable.md?tabs=nodejs): Live metrics is enabled by default.
47
-
*[Python](opentelemetry-enable.md?tabs=python): Live metrics is enabled by default.
*[ASP.NET Core](opentelemetry-enable.md?tabs=aspnetcore): Enabled by default.
45
+
*[Java](./opentelemetry-enable.md?tabs=java): Enabled by default.
46
+
*[Node.js](opentelemetry-enable.md?tabs=nodejs): Enabled by default.
47
+
*[Python](opentelemetry-enable.md?tabs=python): Enabled by default.
48
48
49
49
# [Classic API](#tab/classic)
50
50
51
-
*[ASP.NET](./asp-net.md): Live metrics is enabled by default but can also be [enabled manually using code](./asp-net.md#enable-live-metrics-by-using-code-for-any-.net-application).
52
-
*[ASP.NET Core](./asp-net-core.md): Live metrics is enabled by default but can also be [enabled manually using code](./asp-net-core.md#enable-live-metrics-by-using-code-for-any-.net-application).
53
-
*[.NET/.NET Core Console/Worker](./worker-service.md): Live metrics is enabled by default.
54
-
*[Node.js](./nodejs.md#live-metrics): Live metrics *is not enabled by default*.
51
+
*[ASP.NET](./asp-net.md): Enabled by default but can also be [enabled manually using code](./asp-net.md#enable-live-metrics-by-using-code-for-any-.net-application).
52
+
*[ASP.NET Core](./asp-net-core.md): Enabled by default but can also be [enabled manually using code](./asp-net-core.md#enable-live-metrics-by-using-code-for-any-.net-application).
53
+
*[.NET/.NET Core Console/Worker](./worker-service.md): Enabled by default.
54
+
*[Node.js](./nodejs.md#live-metrics): *Not enabled by default*.
55
55
56
56
---
57
57
@@ -61,7 +61,7 @@ Live metrics is currently supported for ASP.NET, ASP.NET Core, Azure Functions,
## How does live metrics differ from metrics explorer and Log Analytics?
64
+
## How do live metrics differ from metrics explorer and Log Analytics?
65
65
66
66
| Capabilities |Live Stream | Metrics explorer and Log Analytics |
67
67
|---|---|---|
@@ -146,9 +146,9 @@ Basic metrics include request, dependency, and exception rate. Performance metri
146
146
147
147
## Troubleshooting
148
148
149
-
Live metrics uses different IP addresses than other Application Insights telemetry. Make sure [those IP addresses](../ip-addresses.md) are open in your firewall. Also check that [outgoing ports for live metrics](../ip-addresses.md#outgoing-ports) are open in the firewall of your servers.
149
+
Live metrics use different IP addresses than other Application Insights telemetry. Make sure [those IP addresses](../ip-addresses.md) are open in your firewall. Also check that [outgoing ports for live metrics](../ip-addresses.md#outgoing-ports) are open in the firewall of your servers.
150
150
151
-
As described in the [Azure TLS 1.2 migration announcement](https://azure.microsoft.com/updates/azuretls12/), live metrics now only supports TLS 1.2. If you're using an older version of TLS, live metrics doesn't display any data. For applications based on .NET Framework 4.5.1, see [Enable Transport Layer Security (TLS) 1.2 on clients - Configuration Manager](/mem/configmgr/core/plan-design/security/enable-tls-1-2-client#bkmk_net) to support the newer TLS version.
151
+
As described in the [Azure TLS 1.2 migration announcement](https://azure.microsoft.com/updates/azuretls12/), live metrics now only support TLS 1.2. If you're using an older version of TLS, the live metrics pane doesn't display any data. For applications based on .NET Framework 4.5.1, see [Enable Transport Layer Security (TLS) 1.2 on clients - Configuration Manager](/mem/configmgr/core/plan-design/security/enable-tls-1-2-client#bkmk_net) to support the newer TLS version.
152
152
153
153
### Missing configuration for .NET
154
154
@@ -181,7 +181,7 @@ Follow the link to the *Azure status* page and check if there's an activate outa
181
181
182
182
Application Insights SDKs use a REST API to communicate with QuickPulse endpoints, which provide live metrics for your web application. By default, the SDKs poll the endpoints once every five seconds to check if you are viewing the live metrics pane in the Azure portal.
183
183
184
-
If you open the live metrics pane, the SDKs switch to a higher frequency mode and send new metrics to QuickPulse every second. This allows you to monitor and diagnose your live application with 1-second latency, but also generates more network traffic. To restore normal flow of traffic, naviage away from the live metrics pane.
184
+
If you open live metrics, the SDKs switch to a higher frequency mode and send new metrics to QuickPulse every second. This allows you to monitor and diagnose your live application with 1-second latency, but also generates more network traffic. To restore normal flow of traffic, naviage away from the live metrics pane.
185
185
186
186
> [!NOTE]
187
187
> The REST API calls made by the SDKs to QuickPulse endpoints are not tracked by Application Insights and do not affect your dependency calls or other metrics. However, you may see them in other network monitoring tools.
Copy file name to clipboardExpand all lines: articles/azure-monitor/app/worker-service.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -313,7 +313,7 @@ The following sections list the full telemetry automatically collected by Applic
313
313
314
314
### Live metrics
315
315
316
-
[Live metrics](./live-stream.md) can be used to quickly verify if Application Insights monitoring is configured correctly. Although it might take a few minutes before telemetry appears in the portal and analytics, Live metrics shows CPU usage of the running process in near real time. It can also show other telemetry like Requests, Dependencies, and Traces.
316
+
[Live metrics](./live-stream.md) can be used to quickly verify if Application Insights monitoring is configured correctly. Although it might take a few minutes before telemetry appears in the portal and analytics, The live metrics pane shows CPU usage of the running process in near real time. It can also show other telemetry like Requests, Dependencies, and Traces.
0 commit comments