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/continuous-monitoring.md
+40-40Lines changed: 40 additions & 40 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,49 +1,49 @@
1
1
---
2
-
title: Continuous monitoring of your DevOps release pipeline with Azure Pipelines and Azure Application Insights | Microsoft Docs
3
-
description: Provides instructions to quickly set up continuous monitoring with Application Insights
2
+
title: Continuous monitoring of your DevOps release pipeline | Microsoft Docs
3
+
description: This article provides instructions to quickly set up continuous monitoring with Azure Pipelines and Application Insights.
4
4
ms.topic: conceptual
5
5
ms.date: 05/01/2020
6
6
ms.reviewer: vitalyg
7
7
---
8
8
9
9
# Add continuous monitoring to your release pipeline
10
10
11
-
Azure Pipelines integrates with Azure Application Insights to allow continuous monitoring of your DevOps release pipeline throughout the software development lifecycle.
11
+
Azure Pipelines integrates with Application Insights to allow continuous monitoring of your Azure DevOps release pipeline throughout the software development lifecycle.
12
12
13
-
With continuous monitoring, release pipelines can incorporate monitoring data from Application Insights and other Azure resources. When the release pipeline detects an Application Insights alert, the pipeline can gate or roll back the deployment until the alert is resolved. If all checks pass, deployments can proceed automatically from test all the way to production, without the need for manual intervention.
13
+
With continuous monitoring, release pipelines can incorporate monitoring data from Application Insights and other Azure resources. When the release pipeline detects an Application Insights alert, the pipeline can gate or roll back the deployment until the alert is resolved. If all checks pass, deployments can proceed automatically from test all the way to production, without the need for manual intervention.
14
14
15
15
## Configure continuous monitoring
16
16
17
17
1. In [Azure DevOps](https://dev.azure.com), select an organization and project.
18
-
19
-
1. On the left menu of the project page, select **Pipelines** > **Releases**.
20
-
21
-
1. Drop down the arrow next to **New** and select **New release pipeline**. Or, if you don't have a pipeline yet, select **New pipeline** on the page that appears.
22
-
23
-
1. On the **Select a template** pane, search for and select **Azure App Service deployment with continuous monitoring**, and then select **Apply**.
1. On the left menu of the project page, select **Pipelines** > **Releases**.
20
+
21
+
1. Select the dropdown arrow next to **New** and select **New release pipeline**. Or, if you don't have a pipeline yet, select **New pipeline** on the page that appears.
22
+
23
+
1. On the **Select a template** pane, search for and select **Azure App Service deployment with continuous monitoring**, and then select **Apply**.
24
+
25
+
26
26
27
27
1. In the **Stage 1** box, select the hyperlink to **View stage tasks.**
30
30
31
-
1. In the **Stage 1** configuration pane, complete the following fields:
31
+
1. In the **Stage 1** configuration pane, fill in the following fields:
32
32
33
33
| Parameter | Value |
34
34
| ------------- |:-----|
35
-
|**Stage name**| Provide a stage name, or leave it at **Stage 1**. |
36
-
|**Azure subscription**|Drop down and select the linked Azure subscription you want to use.|
37
-
|**App type**|Drop down and select your app type. |
35
+
|**Stage name**| Provide a stage name or leave it at **Stage 1**. |
36
+
|**Azure subscription**|Select the dropdown arrow and select the linked Azure subscription you want to use.|
37
+
|**App type**|Select the dropdown arrow and select your app type. |
38
38
|**App Service name**| Enter the name of your Azure App Service. |
39
-
|**Resource Group name for Application Insights**|Drop down and select the resource group you want to use. |
40
-
| **Application Insights resource name** | Drop down and select the Application Insights resource for the resource group you selected.
39
+
|**Resource Group name for Application Insights**|Select the dropdown arrow and select the resource group you want to use. |
40
+
| **Application Insights resource name** | Select the dropdown arrow and select the Application Insights resource for the resource group you selected.
41
41
42
-
1. To save the pipeline with default alert rule settings, select **Save**at upper right in the Azure DevOps window. Enter a descriptive comment, and then select **OK**.
42
+
1. To save the pipeline with default alert rule settings, select **Save**in the upper-right corner of the Azure DevOps window. Enter a descriptive comment and select **OK**.
43
43
44
44
## Modify alert rules
45
45
46
-
Out of box, the **Azure App Service deployment with continuous monitoring** template has four alert rules: **Availability**, **Failed requests**, **Server response time**, and **Server exceptions**. You can add more rules, or change the rule settings to meet your service level needs.
46
+
Out of the box, the **Azure App Service deployment with continuous monitoring** template has four alert rules: **Availability**, **Failed requests**, **Server response time**, and **Server exceptions**. You can add more rules or change the rule settings to meet your service level needs.
You can modify the script and add additional alert rules, modify the alert conditions, or remove alert rules that don't make sense for your deployment purposes.
62
+
You can modify the script and add more alert rules. You can also modify the alert conditions. And you can remove alert rules that don't make sense for your deployment purposes.
63
63
64
64
## Add deployment conditions
65
65
66
-
When you add deployment gates to your release pipeline, an alert that exceeds the thresholds you set prevents unwanted release promotion. Once you resolve the alert, the deployment can proceed automatically.
66
+
When you add deployment gates to your release pipeline, an alert that exceeds the thresholds you set prevents unwanted release promotion. After you resolve the alert, the deployment can proceed automatically.
67
67
68
68
To add deployment gates:
69
69
70
70
1. On the main pipeline page, under **Stages**, select the **Pre-deployment conditions** or **Post-deployment conditions** symbol, depending on which stage needs a continuous monitoring gate.
1. Under **Evaluation options**, enter the values you want for settings like **The time between re-evaluation of gates** and **The timeout after which gates fail**.
79
+
80
+
81
+
82
+
1. Under **Evaluation options**, enter the values you want for settings like **The time between re-evaluation of gates** and **The timeout after which gates fail**.
83
83
84
84
## View release logs
85
85
86
86
You can see deployment gate behavior and other release steps in the release logs. To open the logs:
87
87
88
-
1. Select **Releases** from the left menu of the pipeline page.
89
-
90
-
1. Select any release.
91
-
92
-
1. Under **Stages**, select any stage to view a release summary.
93
-
94
-
1. To view logs, select **View logs** in the release summary, select the **Succeeded** or **Failed** hyperlink in any stage, or hover over any stage and select **Logs**.
1. Select **Releases** from the left menu of the pipeline page.
89
+
90
+
1. Select any release.
91
+
92
+
1. Under **Stages**, select any stage to view a release summary.
93
+
94
+
1. To view logs, select **View logs** in the release summary, select the **Succeeded** or **Failed** hyperlink in any stage, or hover over any stage and select **Logs**.
95
+
96
+
0 commit comments