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/app-service/tutorial-sre-agent.md
+32-43Lines changed: 32 additions & 43 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -29,7 +29,9 @@ In this tutorial, you will:
29
29
30
30
## Prerequisites
31
31
32
-
To complete this tutorial, you need an [Azure subscription](https://azure.microsoft.com/free/).
32
+
To complete this tutorial, you need:
33
+
- An [Azure subscription](https://azure.microsoft.com/free/).
34
+
- To create the SRE Agent, your account needs Microsoft.Authorization/roleAssignments/write permissions using either Role Based Access Control Administrator or User Access Administrator.
33
35
34
36
## 1. Create an App Service app
35
37
@@ -39,7 +41,6 @@ Start by creating a web app that the SRE Agent can monitor.
39
41
1. In the top search bar, search for **App Services**, then select it from the results.
40
42
1. Select **+ Create** and choose **Web App**.
41
43
42
-
43
44
### Configure the Basics tab
44
45
45
46
In the *Basics* tab, provide the following details:
@@ -87,11 +88,11 @@ Now that your App Service app is created, deploy the sample application from Git
87
88
88
89
1. In the *Settings* tab, configure the following:
1. Repeat the conversion step a few more times to generate additional HTTP 500 errors.
274
-
275
-
> These errors help the SRE Agent detect and diagnose the issue.
267
+
1. Repeat the conversion step a few more times to generate additional HTTP 500 errors. These errors help the SRE Agent detect and diagnose the issue.
276
268
277
269
## 9. Fix the app
278
270
@@ -286,42 +278,39 @@ Now that the app is experiencing failures, use the SRE Agent to diagnose and res
286
278
287
279
1. In the chat box, enter the following command:
288
280
289
-
```text
290
-
What's wrong with my-sre-app?
291
-
```
281
+
```text
282
+
What's wrong with my-sre-app?
283
+
```
292
284
293
285
1. The agent will begin analyzing the app’s health. You’ll see diagnostic messages related to availability, CPU and memory usage, and the recent slot swap.
294
286
295
-
> Each session may vary, but you should see a message similar to:
296
-
>
297
-
> *“I will now perform mitigation for my-sre-app by swapping the slots back to recover the application to a healthy state. Please note that swapping slots back may not always immediately restore health. I will keep you updated on the progress.”*
287
+
> Each session may vary, but you should see a message similar to:
288
+
>
289
+
> *“I will now perform mitigation for my-sre-app by swapping the slots back to recover the application to a healthy state. Please note that swapping slots back may not always immediately restore health. I will keep you updated on the progress.”*
298
290
299
291
1. After a short delay, the agent will prompt you to approve the rollback:
300
292
301
-
> *Performing Slot Swap rollback to Restore Application Availability for my-sre-app*
302
-
> **[Approve]** **[Deny]**
293
+
> *Performing Slot Swap rollback to Restore Application Availability for my-sre-app*
294
+
> **[Approve]** **[Deny]**
303
295
304
296
1. Select **Approve** to initiate the rollback.
305
297
306
298
1. Once the rollback is complete, the agent confirms:
307
299
308
-
> *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:*
309
-
>
310
-
> *• I will ask you for the correct GitHub repo URL to raise an issue for the swap-related downtime.*
311
-
> *• I will monitor the app and provide an availability update in 5 minutes.*
312
-
>
313
-
> *Please provide the GitHub repository URL where you want the issue to be raised.*
300
+
> *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:*
301
+
>
302
+
> *• I will ask you for the correct GitHub repo URL to raise an issue for the swap-related downtime.*
303
+
> *• I will monitor the app and provide an availability update in 5 minutes.*
304
+
>
305
+
> *Please provide the GitHub repository URL where you want the issue to be raised.*
314
306
315
307
## 10. Verify the fix
316
308
317
309
After the SRE Agent rolls back the slot swap, confirm that your app is functioning correctly.
318
310
319
311
1. Open your App Service app in a browser by selecting **Browse** from the **Overview** page.
320
312
321
-
1. In the app interface:
322
-
323
-
- Select **Tools** in the navigation bar.
324
-
- Select **Convert to PNG**.
313
+
1. In the app interface, select **Tools** in the navigation bar and select **Convert to PNG**.
325
314
326
315

0 commit comments