Skip to content

Commit 29a3545

Browse files
committed
screenshots
1 parent 7904289 commit 29a3545

File tree

3 files changed

+23
-23
lines changed

3 files changed

+23
-23
lines changed
111 KB
Loading
63.7 KB
Loading

articles/app-service/tutorial-sre-agent.md

Lines changed: 23 additions & 23 deletions
Original file line numberDiff line numberDiff line change
@@ -87,7 +87,7 @@ Now that your App Service app is created, deploy the sample application from Git
8787
| Property | Value |
8888
|------------|--------------------------------------------------------------|
8989
| Source | **External Git** |
90-
| Repository | `https://github.com/Azure-Samples/App-Service-Agent-Tutorial`|
90+
| Repository | `https://github.com/Azure-Samples/app-service-dotnet-agent-tutorial`|
9191
| Branch | `main` |
9292

9393
1. Select **Save** to apply the deployment settings.
@@ -97,16 +97,12 @@ Now that your App Service app is created, deploy the sample application from Git
9797
After deployment, confirm that the sample app is running as expected.
9898

9999
1. In the left menu of your App Service, select **Overview**.
100-
2. Select **Browse** to open the app in a new browser tab. (It may take a minute to load.)
100+
1. Select **Browse** to open the app in a new browser tab. (It may take a minute to load.)
101101
1. The app displays a large counter and two buttons:
102+
103+
:::image type="content" source="media/tutorial-sre-agent/verify-sample-primary-slot.png" alt-text="Screenshot of the .NET sample in the primary slot." border="false":::
102104

103-
| Button Name | Description |
104-
|------------------------------|---------------------------------------------------------------------------------------------------|
105-
| **Refresh / Throw Exception**| Increments the counter. If error simulation (`INJECT_ERROR` app setting) is enabled, throws an error after a set number of clicks. |
106-
| **Reset Counter** | Resets the counter to zero. |
107-
108-
1. Click the main button several times to observe the counter increase, and verify error behavior if enabled.
109-
105+
1. Select the *Increment* button several times to observe the counter increase.
110106

111107
## 4. Set up a deployment slot for failure simulation
112108

@@ -132,8 +128,8 @@ To simulate an app failure scenario, add a secondary deployment slot.
132128
| Property | Value |
133129
|------------|---------------------------------------------------------------|
134130
| Source | **External Git** |
135-
| Repository | `https://github.com/Azure-Samples/App-Service-Agent-Tutorial` |
136-
| Branch | `broken` |
131+
| Repository | `https://github.com/Azure-Samples/app-service-dotnet-agent-tutorial` |
132+
| Branch | `main` |
137133

138134
1. Select **Save** to apply the deployment settings.
139135

@@ -166,13 +162,13 @@ Now, create an Azure SRE Agent to monitor your App Service app.
166162

167163
1. In the *Create agent* window, enter the following values:
168164

169-
| Property | Value | Remarks |
170-
|------------------|---------------------------|-------------------------------------------------------------------------|
171-
| Subscription | Your Azure subscription | |
172-
| Resource group | `my-sre-agent-group` | New group for the Azure SRE Agent |
173-
| Name | `my-sre-agent`| |
174-
| Region | **Sweden Central** | Required during preview; can monitor resources in any Azure region |
175-
| Choose role | **Contributor** | Grants the agent permission to take action on your behalf |
165+
| Property | Value | Remarks |
166+
|------------------|---------------------------|-------------------------------------------------------------------------|
167+
| Subscription | Your Azure subscription | |
168+
| Resource group | `my-sre-agent-group` | New group for the Azure SRE Agent |
169+
| Name | `my-sre-agent`| |
170+
| Region | **Sweden Central** | Required during preview; can monitor resources in any Azure region |
171+
| Choose role | **Contributor** | Grants the agent permission to take action on your behalf |
176172

177173
1. Select **Select resource groups**.
178174

@@ -221,11 +217,13 @@ Now simulate a failure scenario by swapping to the broken deployment slot.
221217
222218
1. Once the swap is complete, browse to the app’s URL.
223219
224-
1. Select the "Throw Exception" button several times and then refresh the page (using Command-R or F5 button).
220+
:::image type="content" source="media/tutorial-sre-agent/verify-sample-broken-slot.png" alt-text="Screenshot of the .NET sample in the primary slot." border="false":::
221+
222+
1. Select the "Increment" button six times.
225223
226224
1. You should see the app fail and return an HTTP 500 error.
227225
228-
1. Refresh the page a few more times to generate additional HTTP 500 errors, which will help the SRE Agent detect and diagnose the issue.
226+
1. Refresh the page (by pressing Command-R or F5) several times to generate additional HTTP 500 errors, which will help the SRE Agent detect and diagnose the issue.
229227
230228
## 9. Fix the app
231229
@@ -260,8 +258,8 @@ Now that the app is experiencing failures, use the SRE Agent to diagnose and res
260258
261259
> *The slot swap for my-sre-app has been completed successfully (timestamp). The production slot has been restored. I will now continue with post-mitigation steps:*
262260
>
263-
> *I will ask you for the correct GitHub repo URL to raise an issue for the swap-related downtime.* 
264-
> *I will monitor the app and provide an availability update in 5 minutes.* 
261+
> *I will ask you for the correct GitHub repo URL to raise an issue for the swap-related downtime.* 
262+
> *I will monitor the app and provide an availability update in 5 minutes.* 
265263
>
266264
> *Please provide the GitHub repository URL where you want the issue to be raised.*
267265
@@ -271,7 +269,9 @@ After the SRE Agent rolls back the slot swap, confirm that your app is functioni
271269
272270
1. Open your App Service app in a browser by selecting **Browse** from the **Overview** page.
273271
274-
1. Notice the "Throw Exception" button no longer appears and it's been replaced with a "Refresh" button.
272+
1. Notice the text "ERROR INJECTION ENABLED" no longer appears.
273+
274+
1. Select the **Increment** button six times to ensure no errors take place.
275275
276276
## Clean up resources
277277

0 commit comments

Comments
 (0)