Skip to content

Commit d838043

Browse files
made product naming consistent
1 parent e86fd43 commit d838043

File tree

1 file changed

+19
-19
lines changed

1 file changed

+19
-19
lines changed

articles/azure-monitor/app/change-analysis.md

Lines changed: 19 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
2-
title: Use Azure Monitor Application Change Analysis to find web-app issues | Microsoft Docs
3-
description: Use Azure Monitor Application Change Analysis to troubleshoot application issues on live sites on Azure App Service.
2+
title: Use Application Change Analysis in Azure Monitor to find web-app issues | Microsoft Docs
3+
description: Use Application Change Analysis in Azure Monitor to troubleshoot application issues on live sites on Azure App Service.
44
services: application-insights
55
author: cawams
66
manager: carmonm
@@ -12,42 +12,42 @@ ms.date: 05/07/2019
1212
ms.author: cawa
1313
---
1414

15-
# Application Change Analysis (preview)
15+
# Use Application Change Analysis (preview) in Azure Monitor
1616

1717
When a live site issue or outage occurs, quickly determining the root cause is critical. Standard monitoring solutions might alert you to a problem. They might even indicate which component is failing. But this alert won't always immediately explain the failure's cause. You know your site worked five minutes ago, and now it's broken. What changed in the last five minutes? This is the question that Application Change Analysis is designed to answer in Azure Monitor.
1818

19-
Building on the power of [Azure Resource Graph](https://docs.microsoft.com/azure/governance/resource-graph/overview), Application Change Analysis provides insights into your Azure application changes to increase observability and reduce MTTR (mean time to repair).
19+
Building on the power of [Azure Resource Graph](https://docs.microsoft.com/azure/governance/resource-graph/overview), Change Analysis provides insights into your Azure application changes to increase observability and reduce MTTR (mean time to repair).
2020

2121
> [!IMPORTANT]
22-
> Application Change Analysis is currently in preview. This preview version is provided without a service-level agreement. This version is not recommended for production workloads. Some features might not be supported or might have constrained capabilities. For more information, see [Supplemental terms of use for Microsoft Azure previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
22+
> Change Analysis is currently in preview. This preview version is provided without a service-level agreement. This version is not recommended for production workloads. Some features might not be supported or might have constrained capabilities. For more information, see [Supplemental terms of use for Microsoft Azure previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
2323
2424
## Overview
2525

26-
The Change Analysis service detects various types of changes, from the infrastructure layer all the way to application deployment. It's a subscription-level Azure resource provider that checks resource changes in the subscription. The Change Analysis service provides data for various diagnostic tools to help users understand what changes might have caused issues.
26+
Change Analysis detects various types of changes, from the infrastructure layer all the way to application deployment. It's a subscription-level Azure resource provider that checks resource changes in the subscription. Change Analysis provides data for various diagnostic tools to help users understand what changes might have caused issues.
2727

28-
The following diagram illustrates the architecture of the Change Analysis service:
28+
The following diagram illustrates the architecture of Change Analysis:
2929

30-
![Architecture diagram of how the Change Analysis service gets change data and provides it to client tools](./media/change-analysis/overview.png)
30+
![Architecture diagram of how Change Analysis gets change data and provides it to client tools](./media/change-analysis/overview.png)
3131

32-
Currently the Change Analysis tool is integrated into the **Diagnose and solve problems** experience in the App Service web app. To enable change detection and view changes in the web app, see the *Change Analysis for the Web Apps feature* section later in this article.
32+
Currently Change Analysis is integrated into the **Diagnose and solve problems** experience in the App Service web app. To enable change detection and view changes in the web app, see the *Change Analysis for the Web Apps feature* section later in this article.
3333

3434
### Azure Resource Manager deployment changes
3535

36-
Using [Azure Resource Graph](https://docs.microsoft.com/azure/governance/resource-graph/overview), the Change Analysis tool provides a historical record of how the Azure resources that host your application have changed over time. The Change Analysis service can detect, for example, changes in IP configuration rules, managed identities, and SSL settings. So if a tag is added to a web app, the Change Analysis tool reflects the change. This information is available as long as the `Microsoft.ChangeAnalysis` resource provider is enabled in the Azure subscription.
36+
Using [Azure Resource Graph](https://docs.microsoft.com/azure/governance/resource-graph/overview), Change Analysis provides a historical record of how the Azure resources that host your application have changed over time. Change Analysis can detect, for example, changes in IP configuration rules, managed identities, and SSL settings. So if a tag is added to a web app, Change Analysis reflects the change. This information is available as long as the `Microsoft.ChangeAnalysis` resource provider is enabled in the Azure subscription.
3737

3838
### Changes in web app deployment and configuration
3939

40-
The Change Analysis tool captures the deployment and configuration state of an application every 4 hours. It can detect, for example, changes in the application environment variables. The tool computes the differences and presents what has changed. Unlike Resource Manager changes, code deployment change information might not be available immediately in the tool. To view the latest changes in Change Analysis, select **Scan changes now**.
40+
Change Analysis captures the deployment and configuration state of an application every 4 hours. It can detect, for example, changes in the application environment variables. The tool computes the differences and presents what has changed. Unlike Resource Manager changes, code deployment change information might not be available immediately in the tool. To view the latest changes in Change Analysis, select **Scan changes now**.
4141

4242
![Screenshot of the "Scan changes now" button](./media/change-analysis/scan-changes.png)
4343

4444
### Dependency changes
4545

46-
Changes to resource dependencies can also cause issues in a web app. For example, if a web app calls into a Redis cache, the Redis cache SKU could affect the web app performance. To detect changes in dependencies, the Change Analysis service checks the web app's DNS record. In this way, it identifies changes in all app components that could cause issues.
46+
Changes to resource dependencies can also cause issues in a web app. For example, if a web app calls into a Redis cache, the Redis cache SKU could affect the web app performance. To detect changes in dependencies, Change Analysis checks the web app's DNS record. In this way, it identifies changes in all app components that could cause issues.
4747

4848
## Change Analysis for the Web Apps feature
4949

50-
In Azure Monitor, Application Change Analysis is currently built into the self-service **Diagnose and solve problems** experience. Access this experience from the **Overview** page of your App Service application.
50+
In Azure Monitor, Change Analysis is currently built into the self-service **Diagnose and solve problems** experience. Access this experience from the **Overview** page of your App Service application.
5151

5252
![Screenshot of the "Overview" button and the "Diagnose and solve problems" button](./media/change-analysis/change-analysis.png)
5353

@@ -61,7 +61,7 @@ In Azure Monitor, Application Change Analysis is currently built into the self-s
6161

6262
![Screenshot of the "Application Crashes" button](./media/change-analysis/application-crashes-tile.png)
6363

64-
1. To enable the Change Analysis service, select **Enable now**.
64+
1. To enable Change Analysis, select **Enable now**.
6565

6666
![Screenshot of "Application Crashes" options](./media/change-analysis/application-crashes.png)
6767

@@ -73,12 +73,12 @@ In Azure Monitor, Application Change Analysis is currently built into the self-s
7373
- Enable **Scan for code changes** to see deployment files and site configuration changes.
7474
- Enable **Always on** to optimize the performance of change scanning. But keep in mind that this setting might result in additional billing charges.
7575

76-
1. To access the Change Analysis experience, select **Diagnose and solve problems** > **Availability and Performance** > **Application Crashes**. You'll see a graph that summarizes the type of changes over time along with details on those changes:
76+
1. To access Change Analysis, select **Diagnose and solve problems** > **Availability and Performance** > **Application Crashes**. You'll see a graph that summarizes the type of changes over time along with details on those changes:
7777

7878
![Screenshot of the change diff view](./media/change-analysis/change-view.png)
7979

8080

81-
### Enable the Change Analysis service at scale
81+
### Enable Change Analysis at scale
8282

8383
If your subscription includes numerous web apps, enabling the service at the level of the web app would be inefficient. In this case, follow these alternative instructions.
8484

@@ -129,10 +129,10 @@ If your subscription includes numerous web apps, enabling the service at the lev
129129
Set-AzResource -ResourceId <your_webapp_resourceid> -Tag $tag
130130
```
131131
132-
> [!NOTE]
133-
> After you add the hidden tag, you might still need to wait up to 4 hours before you start seeing changes. Results are delayed because the Change Analysis service scans your web app only every 4 hours. The 4-hour schedule limits the scan's performance impact.
132+
> [!NOTE]
133+
> After you add the hidden tag, you might still need to wait up to 4 hours before you start seeing changes. Results are delayed because Change Analysis scans your web app only every 4 hours. The 4-hour schedule limits the scan's performance impact.
134134
135135
## Next steps
136136
137137
- Monitor App Service more effectively by [enabling Application Insights features](azure-web-apps.md) in Azure Monitor.
138-
- Learn more about [Azure Resource Graph](https://docs.microsoft.com/azure/governance/resource-graph/overview), which helps power Application Change Analysis.
138+
- Learn more about [Azure Resource Graph](https://docs.microsoft.com/azure/governance/resource-graph/overview), which helps power Change Analysis.

0 commit comments

Comments
 (0)