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/dev-box/monitor-dev-box.md
+28-24Lines changed: 28 additions & 24 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,9 @@ ms.topic: how-to
8
8
author: delvissantos
9
9
ms.author: delvissantos
10
10
ms.custom: horz-monitor, subject-monitoring
11
-
ms.date: 01/30/2023
11
+
ms.date: 05/29/2024
12
+
13
+
#Customer intent: As a Dev Box administrator, I want to monitor Dev Boxes so that I can ensure that my applications and business processes are running smoothly.
12
14
---
13
15
14
16
# Monitoring Microsoft Dev Box
@@ -33,17 +35,18 @@ See [Create diagnostic setting to collect platform logs and metrics in Azure](/a
33
35
34
36
### Configure Azure diagnostic logs for a dev center
35
37
36
-
With Azure diagnostic logs for DevCenter, you can view audit logs for dataplane operations in your dev center. These logs can be routed to any of the following destinations:
38
+
With Azure diagnostic logs for DevCenter, you can view audit logs for data plane operations in your dev center. These logs can be routed to any of the following destinations:
37
39
38
-
* Azure Storage account
39
-
* Log Analytics workspace
40
+
- Azure Storage account
41
+
- Log Analytics workspace
40
42
41
43
This feature is available on all dev centers.
42
44
43
-
Diagnostics logs allow you to export basic usage information from your dev center to different kinds sources so that you can consume them in a customized way. The dataplane audit logs expose information around CRUD operations for dev boxes within your dev center. Including, for example, start and stop commands executed on dev boxes. Some sample ways you can choose to export this data:
45
+
Diagnostics logs allow you to export basic usage information from your dev center to different kinds sources so that you can consume them in a customized way. The data plane audit logs expose information around CRUD operations for dev boxes within your dev center. Including, for example, start and stop commands executed on dev boxes. Some sample ways you can choose to export this data:
44
46
45
-
* Export data to blob storage, export to CSV.
46
-
* Export data to Azure Monitor logs and view and query data in your own Log Analytics workspace
47
+
- Export data to blob storage
48
+
- Export data to CSV
49
+
- Export data to Azure Monitor logs and view and query data in your own Log Analytics workspace
47
50
48
51
To learn more about the different types of logs available for dev centers, see [DevCenter Diagnostic Logs Reference](monitor-reference.md).
49
52
@@ -53,7 +56,7 @@ Follow these steps enable logging for your Azure DevCenter resource:
53
56
54
57
1. Sign in to the [Azure portal](https://portal.azure.com).
55
58
56
-
2. In the Azure portal, navigate to **All resources** -> **your-devcenter**
59
+
2. In the Azure portal, navigate to your dev center.
57
60
58
61
3. In the **Monitoring** section, select **Diagnostics settings**.
59
62
@@ -66,27 +69,29 @@ To use a storage account to store the logs, follow these steps:
66
69
67
70
>[!NOTE]
68
71
>A storage account in the same region as your dev center is required to complete these steps. Refer to: **[Create an Azure Storage account](../storage/common/storage-account-create.md?tabs=azure-portal&toc=%2fazure%2fstorage%2fblobs%2ftoc.json)** for more information.
69
-
72
+
70
73
1. For **Diagnostic setting name**, enter a name for your diagnostic log settings.
71
74
72
-
2. Select**Archive to a storage account**, then select **Dataplane audit logs**.
73
-
74
-
3. For**Retention (days)**, choose the number of retention days. A retention of zero days stores the logs indefinitely.
1. Under**Destination details**, select **Archive to a storage account**.
75
78
76
-
4. Select the subscription and storage account for the logs.
79
+
1. Select the subscription and storage account for the logs.
77
80
78
-
3. Select **Save**.
81
+
1. Select **Save**.
79
82
80
83
#### Send to Log Analytics
81
84
82
85
To use Log Analytics for the logs, follow these steps:
83
86
84
87
>[!NOTE]
85
88
>A log analytics workspace is required to complete these steps. Refer to: **[Create a Log Analytics workspace in the Azure portal](../azure-monitor/logs/quick-create-workspace.md)** for more information.
86
-
89
+
87
90
1. For **Diagnostic setting name**, enter a name for your diagnostic log settings.
88
91
89
-
2. Select **Send to Log Analytics**, then select **Dataplane audit logs**.
92
+
1. Under **Logs**, select **Dataplane audit logs**.
93
+
94
+
2. Under **Destination details**, select **Send to Log Analytics workspace**.
90
95
91
96
3. Select the subscription and Log Analytics workspace for the logs.
92
97
@@ -106,7 +111,7 @@ The following example shows how to enable diagnostic logs via the Azure PowerShe
106
111
Connect-AzAccount
107
112
```
108
113
109
-
2. To enable Diagnostic Logs in a storage account, enter these commands. Replace the variables with your values:
114
+
2. Enable Diagnostic Logs in a storage account using the following commands. Replace the variables with your values:
110
115
111
116
```azurepowershell-interactive
112
117
$rg = <your-resource-group-name>
@@ -126,7 +131,7 @@ The following example shows how to enable diagnostic logs via the Azure PowerShe
126
131
```azurepowershell-interactive
127
132
Connect-AzAccount
128
133
```
129
-
2. To enable Diagnostic Logs for a Log Analytics workspace, enter these commands. Replace the variables with your values:
134
+
2. Enable Diagnostic Logs for a Log Analytics workspace using the following commands. Replace the variables with your values:
130
135
131
136
```azurepowershell-interactive
132
137
$rg = <your-resource-group-name>
@@ -148,7 +153,7 @@ DevCenter stores data in the following tables.
148
153
149
154
| Table | Description |
150
155
|:---|:---|
151
-
| DevCenterDiagnosticLogs | Table used to store dataplane request/response information on dev box or environments within the dev center. |
156
+
| DevCenterDiagnosticLogs | Table used to store data plane request/response information on dev box or environments within the dev center. |
152
157
| DevCenterResourceOperationLogs | Operation logs pertaining to DevCenter resources, including information around resource health status changes. |
153
158
| DevCenterBillingEventLogs | Billing event related to DevCenter resources. This log contains information about the quantity and unit charged per meter. |
154
159
@@ -157,20 +162,20 @@ After enabling diagnostic settings on your dev center, you should be able to vie
157
162
158
163
Here are some queries that you can enter into Log search to help your monitor your dev boxes.
159
164
160
-
To query for all dataplane logs from DevCenter:
165
+
To query for all data plane logs from DevCenter:
161
166
162
167
```kusto
163
168
DevCenterDiagnosticLogs
164
169
```
165
170
166
-
To query for a filtered list of dataplane logs, specific to a single devbox:
171
+
To query for a filtered list of data plane logs, specific to a single devbox:
167
172
168
173
```kusto
169
174
DevCenterDiagnosticLogs
170
175
| where TargetResourceId contains "<devbox-name>"
171
176
```
172
177
173
-
To generate a chart for dataplane logs, grouped by operation result status:
178
+
To generate a chart for data plane logs, grouped by operation result status:
174
179
175
180
```kusto
176
181
DevCenterDiagnosticLogs
@@ -184,5 +189,4 @@ These examples are just a small sample of the rich queries that can be performed
0 commit comments