|
1 | 1 | --- |
2 | | -title: DevCenter Diagnostic Logs Reference |
| 2 | +title: Dev center (DevCenter) diagnostic logs reference |
3 | 3 | 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. |
5 | 5 | services: dev-box |
6 | 6 | ms.service: dev-box |
7 | | -ms.topic: troubleshooting |
| 7 | +ms.topic: conceptual-article |
8 | 8 | author: delvissantos |
9 | 9 | ms.author: delvissantos |
10 | | -ms.date: 04/28/2023 |
| 10 | +ms.date: 01/11/2024 |
11 | 11 | --- |
12 | 12 |
|
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 |
16 | 14 |
|
| 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). |
17 | 16 |
|
18 | 17 | ## Resource logs |
19 | 18 |
|
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`. |
21 | 20 |
|
22 | 21 | | Azure Storage field or property | Azure Monitor Logs property | Description | |
23 | 22 | | --- | --- | --- | |
24 | 23 | | **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>`). | |
27 | 26 | | **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`. | |
29 | 28 | | **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. | |
32 | 31 |
|
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). |
34 | 33 |
|
35 | 34 | ## Azure Monitor Logs tables |
36 | 35 |
|
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. |
| 36 | +<!-- Rose: The target link doesn't provide -- "a list of Kusto tables that a dev center uses" and the target title is completely wrong. |
| 37 | + Would this link be more correct? |
| 38 | + https://learn.microsoft.com/en-us/azure/azure-monitor/reference/tables/tables-resourcetype#dev-centers |
| 39 | + Title = "Azure Monitor Logs table reference organized by resource type > Dev Centers" |
| 40 | +--> |
38 | 41 |
|
39 | | -## Next steps |
| 42 | +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](how-to-configure-dev-box-azure-diagnostic-logs.md) article. |
40 | 43 |
|
41 | | -For more information on monitoring DevCenter resources, see the following articles: |
| 44 | +## Related content |
42 | 45 |
|
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). |
| 46 | +- [Configure Azure diagnostic logs for a dev center](how-to-configure-dev-box-azure-diagnostic-logs.md) |
| 47 | +- [Monitor Azure resources with Azure Monitor](../azure-monitor/essentials/monitor-azure-resource.md) |
0 commit comments