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/annotations.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -170,7 +170,7 @@ To create release annotations, install one of the many Azure DevOps extensions a
170
170
171
171
1. On the **Visual Studio Marketplace** [Release Annotations extension](https://marketplace.visualstudio.com/items/ms-appinsights.appinsightsreleaseannotations) page, select your Azure DevOps organization. Select **Install** to add the extension to your Azure DevOps organization.
172
172
173
-

173
+
:::image type="content" source="./media/annotations/1-install.png" lightbox="./media/annotations/1-install.png" alt-text="Screenshot that shows selecting an Azure DevOps organization and selecting Install.":::
174
174
175
175
You only need to install the extension once for your Azure DevOps organization. You can now configure release annotations for any project in your organization.
176
176
@@ -182,34 +182,34 @@ Create a separate API key for each of your Azure Pipelines release templates.
182
182
183
183
1. Open the **API Access** tab and copy the **Application Insights ID**.
184
184
185
-

185
+
:::image type="content" source="./media/annotations/2-app-id.png" lightbox="./media/annotations/2-app-id.png" alt-text="Screenshot that shows under API Access, copying the Application ID.":::
186
186
187
187
1. In a separate browser window, open or create the release template that manages your Azure Pipelines deployments.
188
188
189
189
1. Select **Add task** and then select the **Application Insights Release Annotation** task from the menu.
190
190
191
-

191
+
:::image type="content" source="./media/annotations/3-add-task.png" lightbox="./media/annotations/3-add-task.png" alt-text="Screenshot that shows selecting Add Task and Application Insights Release Annotation.":::
192
192
193
193
> [!NOTE]
194
194
> The Release Annotation task currently supports only Windows-based agents. It won't run on Linux, macOS, or other types of agents.
195
195
196
196
1. Under **Application ID**, paste the Application Insights ID you copied from the **API Access** tab.
197
197
198
-

198
+
:::image type="content" source="./media/annotations/4-paste-app-id.png" lightbox="./media/annotations/4-paste-app-id.png" alt-text="Screenshot that shows pasting the Application Insights ID.":::
199
199
200
200
1. Back in the Application Insights **API Access** window, select **Create API Key**.
201
201
202
-

202
+
:::image type="content" source="./media/annotations/5-create-api-key.png" lightbox="./media/annotations/5-create-api-key.png" alt-text="Screenshot that shows selecting the Create API Key on the API Access tab.":::
203
203
204
204
1. In the **Create API key** window, enter a description, select **Write annotations**, and then select **Generate key**. Copy the new key.
205
205
206
-

206
+
:::image type="content" source="./media/annotations/6-create-api-key.png" lightbox="./media/annotations/6-create-api-key.png" alt-text="Screenshot that shows in the Create API key window, entering a description, selecting Write annotations, and then selecting the Generate key.":::
207
207
208
208
1. In the release template window, on the **Variables** tab, select **Add** to create a variable definition for the new API key.
209
209
210
210
1. Under **Name**, enter **ApiKey**. Under **Value**, paste the API key you copied from the **API Access** tab.
211
211
212
-

212
+
:::image type="content" source="./media/annotations/7-paste-api-key.png" lightbox="./media/annotations/7-paste-api-key.png" alt-text="Screenshot that shows in the Azure DevOps Variables tab, selecting Add, naming the variable ApiKey, and pasting the API key under Value.":::
213
213
214
214
1. Select **Save** in the main release template window to save the template.
Copy file name to clipboardExpand all lines: articles/azure-monitor/app/api-custom-events-metrics.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -351,7 +351,7 @@ Telemetry items reported within a scope of operation become children of such an
351
351
352
352
In **Search**, the operation context is used to create the **Related Items** list.
353
353
354
-

354
+
:::image type="content" source="./media/api-custom-events-metrics/21.png" lightbox="./media/api-custom-events-metrics/21.png" alt-text="Screenshot that shows the Related Items list.":::
355
355
356
356
For more information on custom operations tracking, see [Track custom operations with Application Insights .NET SDK](./custom-operations-tracking.md).
Copy file name to clipboardExpand all lines: articles/azure-monitor/app/app-map.md
+14-14Lines changed: 14 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -34,53 +34,53 @@ When you select **Update map components**, the map is refreshed with all compone
34
34
35
35
If all the components are roles within a single Application Insights resource, this discovery step isn't required. The initial load for such an application will have all its components.
36
36
37
-

37
+
:::image type="content" source="media/app-map/app-map-001.png" lightbox="media/app-map/app-map-001.png" alt-text="Screenshot that shows an example of an application map.":::
38
38
39
39
One of the key objectives with this experience is to be able to visualize complex topologies with hundreds of components.
40
40
41
41
Select any component to see related insights and go to the performance and failure triage experience for that component.
42
42
43
-

43
+
:::image type="content" source="media/app-map/application-map-002.png" lightbox="media/app-map/application-map-002.png" alt-text="Diagram that shows application map details.":::
44
44
45
45
### Investigate failures
46
46
47
47
Select **Investigate failures** to open the **Failures** pane.
48
48
49
-

49
+
:::image type="content" source="media/app-map/investigate-failures.png" lightbox="media/app-map/investigate-failures.png" alt-text="Screenshot that shows the Investigate failures button.":::
50
50
51
-

51
+
:::image type="content" source="media/app-map/failures.png" lightbox="media/app-map/failures.png" alt-text="Screenshot that shows the Failures screen.":::
52
52
53
53
### Investigate performance
54
54
55
55
To troubleshoot performance problems, select **Investigate performance**.
56
56
57
-

57
+
:::image type="content" source="media/app-map/investigate-performance.png" lightbox="media/app-map/investigate-performance.png" alt-text="Screenshot that shows the Investigate performance button.":::
58
58
59
-

59
+
:::image type="content" source="media/app-map/performance.png" lightbox="media/app-map/performance.png" alt-text="Screenshot that shows the Performance screen.":::
60
60
61
61
### Go to details
62
62
63
63
The **Go to details** button displays the end-to-end transaction experience, which offers views at the call stack level.
64
64
65
-

65
+
:::image type="content" source="media/app-map/go-to-details.png" lightbox="media/app-map/go-to-details.png" alt-text="Screenshot that shows the Go to details button.":::
66
66
67
-

67
+
:::image type="content" source="media/app-map/end-to-end-transaction.png" lightbox="media/app-map/end-to-end-transaction.png" alt-text="Screenshot that shows the End-to-end transaction details screen.":::
68
68
69
69
### View in Logs (Analytics)
70
70
71
71
To query and investigate your applications data further, select **View in Logs (Analytics)**.
72
72
73
-

73
+
:::image type="content" source="media/app-map/view-logs.png" lightbox="media/app-map/view-logs.png" alt-text="Screenshot that shows the View in Logs (Analytics) button.":::
74
74
75
-

75
+
:::image type="content" source="media/app-map/log-analytics.png" lightbox="media/app-map/log-analytics.png" alt-text="Screenshot that shows the Logs screen with a line graph that summarizes the average response duration of a request over the past 12 hours.":::
76
76
77
77
### Alerts
78
78
79
79
To view active alerts and the underlying rules that cause the alerts to be triggered, select **Alerts**.
80
80
81
-

81
+
:::image type="content" source="media/app-map/alerts.png" lightbox="media/app-map/alerts.png" alt-text="Screenshot that shows the Alerts button.":::
82
82
83
-

83
+
:::image type="content" source="media/app-map/alerts-view.png" lightbox="media/app-map/alerts-view.png" alt-text="Screenshot that shows a list of alerts.":::
To help you understand the concept of *cloud role names*, look at an application map that has multiple cloud role names present.
228
228
229
-

229
+
:::image type="content" source="media/app-map/cloud-rolename.png" lightbox="media/app-map/cloud-rolename.png" alt-text="Screenshot that shows an application map example.":::
230
230
231
231
In the application map shown, each of the names in green boxes is a cloud role name value for different aspects of this particular distributed application. For this app, its roles consist of `Authentication`, `acmefrontend`, `Inventory Management`, and `Payment Processing Worker Role`.
232
232
@@ -568,7 +568,7 @@ Enable **Intelligent view** only for a single Application Insights resource.
568
568
569
569
To provide feedback, use the feedback option.
570
570
571
-

571
+
:::image type="content" source="./media/app-map/14-updated.png" lightbox="./media/app-map/14-updated.png" alt-text="Screenshot that shows the Feedback option.":::
0 commit comments