Skip to content

Commit 49647ce

Browse files
Merge pull request #263046 from GitHubber17/183368-22
Freshness | Microsoft Dev Box procedures
2 parents fe63001 + ec3b055 commit 49647ce

File tree

1 file changed

+17
-20
lines changed

1 file changed

+17
-20
lines changed

articles/dev-box/monitor-reference.md

Lines changed: 17 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -1,44 +1,41 @@
11
---
2-
title: DevCenter Diagnostic Logs Reference
2+
title: Dev center (DevCenter) diagnostic logs reference
33
titleSuffix: Microsoft Dev Box
4-
description: Reference for the schema for Dev Center Diagnostic logs
4+
description: Schema reference for dev center (DevCenter) diagnostic logs. Review the list of Azure Storage and Azure Monitor Logs properties included in monitoring data.
55
services: dev-box
66
ms.service: dev-box
7-
ms.topic: troubleshooting
7+
ms.topic: reference
88
author: delvissantos
99
ms.author: delvissantos
10-
ms.date: 04/28/2023
10+
ms.date: 01/17/2024
1111
---
1212

13-
# Monitoring Microsoft DevCenter data reference
14-
15-
This article provides a reference for log and metric data collected to analyze the performance and availability of resources within your dev center. See the [How To Monitor DevCenter Diagnostic Logs](how-to-configure-dev-box-azure-diagnostic-logs.md) article for details on collecting and analyzing monitoring data for a dev center.
13+
# Microsoft dev center monitoring data reference
1614

15+
This article provides a reference for log and metric data collected for a Microsoft Dev Box dev center. You can use the collected data to analyze the performance and availability of resources within your dev center. For details about how to collect and analyze monitoring data for your dev center, see [Configure Azure diagnostic logs for a dev center](how-to-configure-dev-box-azure-diagnostic-logs.md).
1716

1817
## Resource logs
1918

20-
The following table lists the properties of resource logs in DevCenter. The resource logs are collected into Azure Monitor Logs or Azure Storage. In Azure Monitor, logs are collected in the **DevCenterDiagnosticLogs** table under the resource provider name of `MICROSOFT.DEVCENTER`.
19+
The following table lists the properties of resource logs in a dev center. The resource logs are collected into Azure Monitor Logs or Azure Storage. In Azure Monitor, logs are collected in the **DevCenterDiagnosticLogs** table under the resource provider name of `MICROSOFT.DEVCENTER`.
2120

2221
| Azure Storage field or property | Azure Monitor Logs property | Description |
2322
| --- | --- | --- |
2423
| **time** | **TimeGenerated** | The date and time (UTC) when the operation occurred. |
25-
| **resourceId** | **ResourceId** | The DevCenter resource for which logs are enabled.|
26-
| **operationName** | **OperationName** | Name of the operation. If the event represents an Azure role-based access control (RBAC) operation, specify the Azure RBAC operation name (for example, `Microsoft.DevCenter/projects/users/devboxes/write`). This name is typically modeled in the form of an Azure Resource Manager operation, even if it's not a documented Resource Manager operation: (`Microsoft.<providerName>/<resourceType>/<subtype>/<Write/Read/Delete/Action>`)|
24+
| **resourceId** | **ResourceId** | The dev center resource for which logs are enabled. |
25+
| **operationName** | **OperationName** | Name of the operation. If the event represents an Azure role-based access control (RBAC) operation, specify the Azure RBAC operation name (for example, `Microsoft.DevCenter/projects/users/devboxes/write`). This name is typically modeled in the form of an Azure Resource Manager operation, even if it's not a documented Resource Manager operation: (`Microsoft.<providerName>/<resourceType>/<subtype>/<Write/Read/Delete/Action>`). |
2726
| **identity** | **CallerIdentity** | The OID of the caller of the event. |
28-
| **TargetResourceId** | **ResourceId** | The subresource that pertains to the request. Depending on the operation performed, this value may point to a `devbox` or `environment`.|
27+
| **TargetResourceId** | **ResourceId** | The subresource that pertains to the request. Depending on the operation performed, this value might point to a `devbox` or `environment`. |
2928
| **resultSignature** | **ResponseCode** | The HTTP status code returned for the operation. |
30-
| **resultType** | **OperationResult** | Whether the operation failed or succeeded. |
31-
| **correlationId** | **CorrelationId** | The unique correlation ID for the operation that can be shared with the app team if investigations are necessary.|
29+
| **resultType** | **OperationResult** | Indicates whether the operation failed or succeeded. |
30+
| **correlationId** | **CorrelationId** | The unique correlation ID for the operation that can be shared with the app team to support further investigation. |
3231

33-
For a list of all Azure Monitor log categories and links to associated schemas, see [Azure Monitor Logs categories and schemas](../azure-monitor/essentials/resource-logs-schema.md).
32+
For a list of all Azure Monitor log categories and links to associated schemas, see [Common and service-specific schemas for Azure resource logs](../azure-monitor/essentials/resource-logs-schema.md).
3433

3534
## Azure Monitor Logs tables
3635

37-
DevCenter uses Kusto tables from Azure Monitor Logs. You can query these tables with Log analytics. For a list of Kusto tables DevCenter uses, see the [Azure Monitor Logs table reference](how-to-configure-dev-box-azure-diagnostic-logs.md) article.
38-
39-
## Next steps
36+
A dev center uses Kusto tables from Azure Monitor Logs. You can query these tables with Log Analytics. For a list of Kusto tables that a dev center uses, see the [Azure Monitor Logs table reference organized by resource type](/azure/azure-monitor/reference/tables/tables-resourcetype#dev-centers).
4037

41-
For more information on monitoring DevCenter resources, see the following articles:
38+
## Related content
4239

43-
- To learn how to configure Azure diagnostic logs for a dev center, see [Configure Azure diagnostic logs for a DevCenter](how-to-configure-dev-box-azure-diagnostic-logs.md).
44-
- For details on monitoring Azure resources, see [Monitoring Azure resources with Azure Monitor](../azure-monitor/essentials/monitor-azure-resource.md).
40+
- [Configure Azure diagnostic logs for a dev center](how-to-configure-dev-box-azure-diagnostic-logs.md)
41+
- [Monitor Azure resources with Azure Monitor](../azure-monitor/essentials/monitor-azure-resource.md)

0 commit comments

Comments
 (0)