Skip to content

Commit 9059b41

Browse files
Merge pull request #276665 from RoseHJM/mdb-freshness-03
MDB - freshness 03 - monitoring
2 parents 2cff457 + a98c709 commit 9059b41

File tree

1 file changed

+28
-24
lines changed

1 file changed

+28
-24
lines changed

articles/dev-box/monitor-dev-box.md

Lines changed: 28 additions & 24 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,9 @@ ms.topic: how-to
88
author: delvissantos
99
ms.author: delvissantos
1010
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.
1214
---
1315

1416
# Monitoring Microsoft Dev Box
@@ -33,17 +35,18 @@ See [Create diagnostic setting to collect platform logs and metrics in Azure](/a
3335

3436
### Configure Azure diagnostic logs for a dev center
3537

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:
3739

38-
* Azure Storage account
39-
* Log Analytics workspace
40+
- Azure Storage account
41+
- Log Analytics workspace
4042

4143
This feature is available on all dev centers.
4244

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:
4446

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
4750

4851
To learn more about the different types of logs available for dev centers, see [DevCenter Diagnostic Logs Reference](monitor-reference.md).
4952

@@ -53,7 +56,7 @@ Follow these steps enable logging for your Azure DevCenter resource:
5356

5457
1. Sign in to the [Azure portal](https://portal.azure.com).
5558

56-
2. In the Azure portal, navigate to **All resources** -> **your-devcenter**
59+
2. In the Azure portal, navigate to your dev center.
5760

5861
3. In the **Monitoring** section, select **Diagnostics settings**.
5962

@@ -66,27 +69,29 @@ To use a storage account to store the logs, follow these steps:
6669

6770
>[!NOTE]
6871
>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+
7073
1. For **Diagnostic setting name**, enter a name for your diagnostic log settings.
7174

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.
75+
1. Under **Logs**, select **Dataplane audit logs**.
76+
77+
1. Under **Destination details**, select **Archive to a storage account**.
7578

76-
4. Select the subscription and storage account for the logs.
79+
1. Select the subscription and storage account for the logs.
7780

78-
3. Select **Save**.
81+
1. Select **Save**.
7982

8083
#### Send to Log Analytics
8184

8285
To use Log Analytics for the logs, follow these steps:
8386

8487
>[!NOTE]
8588
>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+
8790
1. For **Diagnostic setting name**, enter a name for your diagnostic log settings.
8891

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**.
9095

9196
3. Select the subscription and Log Analytics workspace for the logs.
9297

@@ -106,7 +111,7 @@ The following example shows how to enable diagnostic logs via the Azure PowerShe
106111
Connect-AzAccount
107112
```
108113
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:
110115
111116
```azurepowershell-interactive
112117
$rg = <your-resource-group-name>
@@ -126,7 +131,7 @@ The following example shows how to enable diagnostic logs via the Azure PowerShe
126131
```azurepowershell-interactive
127132
Connect-AzAccount
128133
```
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:
130135
131136
```azurepowershell-interactive
132137
$rg = <your-resource-group-name>
@@ -148,7 +153,7 @@ DevCenter stores data in the following tables.
148153
149154
| Table | Description |
150155
|:---|:---|
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. |
152157
| DevCenterResourceOperationLogs | Operation logs pertaining to DevCenter resources, including information around resource health status changes. |
153158
| DevCenterBillingEventLogs | Billing event related to DevCenter resources. This log contains information about the quantity and unit charged per meter. |
154159
@@ -157,20 +162,20 @@ After enabling diagnostic settings on your dev center, you should be able to vie
157162
158163
Here are some queries that you can enter into Log search to help your monitor your dev boxes.
159164
160-
To query for all dataplane logs from DevCenter:
165+
To query for all data plane logs from DevCenter:
161166
162167
```kusto
163168
DevCenterDiagnosticLogs
164169
```
165170

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:
167172

168173
```kusto
169174
DevCenterDiagnosticLogs
170175
| where TargetResourceId contains "<devbox-name>"
171176
```
172177

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:
174179

175180
```kusto
176181
DevCenterDiagnosticLogs
@@ -184,5 +189,4 @@ These examples are just a small sample of the rich queries that can be performed
184189

185190
- [Monitor Dev Box](monitor-dev-box.md)
186191
- [Azure Diagnostic logs](../azure-monitor/essentials/platform-logs-overview.md)
187-
- [Azure Monitor logs](../azure-monitor/logs/log-query-overview.md)
188-
- [Azure Log Analytics REST API](/rest/api/loganalytics)
192+
- [Azure Monitor logs](../azure-monitor/logs/log-query-overview.md)

0 commit comments

Comments
 (0)