Skip to content

Commit a565060

Browse files
committed
updates to overview
1 parent 5d13b89 commit a565060

File tree

1 file changed

+9
-9
lines changed

1 file changed

+9
-9
lines changed

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

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -66,8 +66,8 @@ Azure Monitor Change Analysis service supports resource property level changes i
6666

6767
Azure Monitor's Change Analysis queries for:
6868
- [Azure Resource Manager resource properties.](#azure-resource-manager-resource-properties-changes)
69-
- [Configuration changes.](#configuration-changes)
70-
- [Web app in-guest changes.](#changes-in-azure-functions-and-web-app-configuration-in-guest-changes)
69+
- [Resource configuration changes.](#resource-configuration-changes)
70+
- [App Service Function and Web App in-guest changes.](#changes-in-azure-app-services-function-and-web-apps-in-guest-changes)
7171

7272
Change Analysis also tracks [resource dependency changes](#dependency-changes) to diagnose and monitor an application end-to-end.
7373

@@ -78,7 +78,7 @@ Using [Azure Resource Graph](../../governance/resource-graph/overview.md), Chang
7878
- Platform OS upgrade
7979
- Hostnames
8080

81-
### Configuration changes
81+
### Resource configuration changes
8282

8383
In addition to the settings set via Azure Resource Manager, you can set configuration settings using the CLI, Bicep, etc., such as:
8484
- IP Configuration rules
@@ -87,13 +87,13 @@ In addition to the settings set via Azure Resource Manager, you can set configur
8787

8888
These setting changes are not captured by Azure Resource Graph. Change Analysis fills this gap by capturing snapshots of changes in those main configuration properties, like changes to the connection string, etc. Snapshots are taken of configuration changes and change details every up to 6 hours. [See known limitations.](#limitations)
8989

90-
### Changes in Azure Functions and web app configuration (in-guest changes)
90+
### Changes in Azure App Services Function and Web Apps (in-guest changes)
9191

92-
Every 30 minutes, Change Analysis captures the configuration state of a web application. For example, it can detect changes in the application environment variables. The tool computes the differences and presents the changes.
92+
Every 30 minutes, Change Analysis captures the configuration state of a web application. For example, it can detect changes in the application environment variables, configuration files, and WebJobs. The tool computes the differences and presents the changes.
9393

9494
:::image type="content" source="./media/change-analysis/scan-changes.png" alt-text="Screenshot of the Scan changes now button":::
9595

96-
If you don't see changes within 30 minutes, refer to [our troubleshooting guide](./change-analysis-troubleshoot.md#cannot-see-in-guest-changes-for-newly-enabled-web-app).
96+
If you don't see file changes within 30 minutes or configuration changes within 6 hours, refer to [our troubleshooting guide](./change-analysis-troubleshoot.md#cannot-see-in-guest-changes-for-newly-enabled-web-app). [See known limitations.](#limitations)
9797

9898
Currently, all text-based files under site root **wwwroot** with the following extensions are supported:
9999

@@ -129,10 +129,10 @@ Currently the following dependencies are supported in **Web App Diagnose and sol
129129

130130
## Limitations
131131

132-
- **OS environment**: Change Analysis currently only works with Windows environments, not Linux.
132+
- **OS environment**: For Azure App Services Function and Web App in-guest changes, Change Analysis currently only works with Windows environments, not Linux.
133133
- **Web app deployment changes**: Code deployment change information might not be available immediately in the Change Analysis tool. To view the latest changes in Change Analysis, select **Refresh**.
134-
- **File changes**: File changes take up to 30 minutes to display.
135-
- **Configuration changes**: Due to the snapshot approach to configuration changes, timestamps of configuration changes could show as up to 6 hours from when the change actually happened.
134+
- **App Services file changes**: File changes take up to 30 minutes to display.
135+
- **App Services configuration changes**: Due to the snapshot approach to configuration changes, timestamps of configuration changes could take up to 6 hours to display from when the change actually happened.
136136

137137
## Next steps
138138

0 commit comments

Comments
 (0)