监视 Azure IoT 中心数据参考Monitoring Azure IoT Hub data reference

• 10/22/2020
• • r

请参阅监视 Azure IoT 中心，详细了解如何收集和分析 Azure IoT 中心的监视数据。See Monitor Azure IoT Hub for details on collecting and analyzing monitoring data for Azure IoT Hub.

指标Metrics

本节列出了 Azure IoT 中心自动收集的所有平台指标。This section lists all the automatically collected platform metrics for Azure IoT Hub. IoT 中心指标的资源提供程序命名空间为 Microsoft.Devices，类型命名空间为 IoTHubs 。The resource provider namespace for IoT Hub metrics is Microsoft.Devices and the type Namespace is IoTHubs.

以下小节按常规类别细分了 IoT 中心平台指标，并按它们在 Azure 门户中显示的名称列出它们。The following subsections break out the IoT Hub platform metrics by general category and list them by the display name that they appear in the Azure portal with. 还提供了与每个小节中显示的指标相关的信息。Information is also provided relevant to the metrics that appear in each subsection.

你还可以在 Azure Monitor 文档中的 Microsoft.Devices/IotHubs 下找到一个按指标名称列出所有 IoT 中心平台指标的表。You can also find a single table that lists all of the IoT Hub platform metrics by metric name under Microsoft.Devices/IotHubs in the Azure Monitor documentation. 请注意，此表并不提供本文中涵盖的一些信息，如一些指标支持的聚合。Be aware that this table does not provide some of the information, like supported aggregations for some metrics, available in this article.

若要了解其他 Azure 服务支持的指标，请参阅 Azure Monitor 支持的指标。To learn about metrics supported by other Azure services, see Supported metrics with Azure Monitor.

本节主题Topics in this section

• 支持的聚合Supported aggregations
• 云到设备命令指标Cloud to device command metrics
• 云到设备直接方法指标Cloud to device direct methods metrics
• 云到设备孪生操作指标Cloud to device twin operations metrics
• 配置指标Configurations metrics
• 每日配额指标Daily quota metrics
• 设备指标Device metrics
• 设备遥测指标Device telemetry metrics
• 设备到云孪生操作指标Device to cloud twin operations metrics
• 事件网格指标Event grid metrics
• 作业指标Jobs metrics
• 路由指标Routing metrics
• 孪生查询指标Twin query metrics

支持的聚合Supported aggregations

每个表中的“聚合类型”列对应于为图表或警报选择指标时使用的默认聚合。The Aggregation Type column in each table corresponds to the default aggregation that is used when the metric is selected for a chart or alert.

对于大多数指标，所有聚合类型都是有效的；但是，对于计数指标，即“计价单位”列值为“计数”的指标，只有一些聚合是有效的 。For most metrics, all aggregation types are valid; however, for count metrics, those with a Unit column value of Count, only some aggregations are valid. 计数指标可以是以下两种类型之一：Count metrics can be one of two types:

• 对于单点计数指标，IoT 中心每次执行测量操作时都会注册一个数据点（实质上为 1）。For Single-point count metrics, IoT Hub registers a single data point -- essentially a 1 -- every time the measured operation occurs. 然后 Azure Monitor 在指定的粒度上对这些数据点进行求和。Azure Monitor then sums these data points over the specified granularity. 单点指标的示例有发送的遥测消息数和已完成的 C2D 消息传递次数 。Examples of Single-point metrics are Telemetry messages sent and C2D message deliveries completed. 对于这些指标，唯一相关的聚合类型为总计（总和）。For these metrics, the only relevant aggregation type is Total (Sum). 通过门户可选择最小值、最大值和平均值；然而，这些值始终为 1。The portal allows you to choose minimum, maximum, and average; however, these values will always be 1.

• 对于快照计数指标，当进行测量操作时，IoT 中心将登记总计数。For Snapshot count metrics, IoT Hub registers a total count when the measured operation occurs. 当前，IoT 中心发布了三种快照指标：已使用的消息总数、设备总数（预览）和已连接设备数（预览） 。Currently, there are three Snapshot metrics emitted by IoT Hub: Total number of messages used, Total devices (preview), and Connected devices (preview). 因为这些指标在每次发出时都显示一个“总数”，所以在指定的粒度上对它们进行求和没有任何意义。Because these metrics present a "total" quantity every time they are emitted, summing them over the specified granularity makes no sense. Azure Monitor 仅限为这些指标的聚合类型选择平均值、最小值和最大值。Azure Monitor limits you to selecting average, minimum, and maximum for the aggregation type for these metrics.

云到设备命令指标Cloud to device command metrics

对于“计价单位”值为“计数”的指标，只有总计（总和）聚合有效 。For metrics with a Unit value of Count, only total (sum) aggregation is valid. 最小值、最大值和平均值聚合始终返回 1。Minimum, maximum, and average aggregations always return 1. 有关详细信息，请参阅支持的聚合。For more information, see Supported aggregations.

云到设备直接方法指标Cloud to device direct methods metrics

对于“计价单位”值为“计数”的指标，只有总计（总和）聚合有效 。For metrics with a Unit value of Count only total (sum) aggregation is valid. 最小值、最大值和平均值聚合始终返回 1。Minimum, maximum, and average aggregations always return 1. 有关详细信息，请参阅支持的聚合。For more information, see Supported aggregations.

云到设备孪生操作指标Cloud to device twin operations metrics

对于“计价单位”值为“计数”的指标，只有总计（总和）聚合有效 。For metrics with a Unit value of Count, only total (sum) aggregation is valid. 最小值、最大值和平均值聚合始终返回 1。Minimum, maximum, and average aggregations always return 1. 有关详细信息，请参阅支持的聚合。For more information, see Supported aggregations.

配置指标Configurations metrics

对于“计价单位”值为“计数”的指标，只有总计（总和）聚合有效 。For metrics with a Unit value of Count, only total (sum) aggregation is valid. 最小值、最大值和平均值聚合始终返回 1。Minimum, maximum, and average aggregations always return 1. 有关详细信息，请参阅支持的聚合。For more information, see Supported aggregations.

每日配额指标Daily quota metrics

对于“已使用的消息总数”，只支持最小值、最大值和平均值聚合。For Total number of messages used, only minimum, maximum, and average aggregations are supported. 有关详细信息，请参阅支持的聚合。For more information, see Supported aggregations.

设备指标Device metrics

对于设备总数（已弃用）和连接的设备数（已弃用），只有总计（总和）聚合有效 。For Total devices (deprecated) and Connected devices (deprecated), only total (sum) aggregation is valid. 最小值、最大值和平均值聚合始终返回 1。Minimum, maximum, and average aggregations always return 1. 有关详细信息，请参阅支持的聚合。For more information, see Supported aggregations.

对于设备总数（预览）和已连接设备数（预览），只有最小值、最大值和平均值聚合有效 。For Total devices (preview) and Connected devices (preview), only minimum, maximum, and average aggregations are valid. 有关详细信息，请参阅支持的聚合。For more information, see Supported aggregations.

已连接设备数（预览）和设备总数（预览）不能通过诊断设置导出 。Connected devices (preview) and Total devices (preview) are not exportable via diagnostic settings.

设备遥测指标Device telemetry metrics

对于“计价单位”值为“计数”的指标，只有总计（总和）聚合有效 。For metrics with a Unit value of Count, only total (sum) aggregation is valid. 最小值、最大值和平均值聚合始终返回 1。Minimum, maximum, and average aggregations always return 1. 有关详细信息，请参阅支持的聚合。For more information, see Supported aggregations.

设备到云孪生操作指标Device to cloud twin operations metrics

对于“计价单位”值为“计数”的指标，只有总计（总和）聚合有效 。For metrics with a Unit value of Count, only total (sum) aggregation is valid. 最小值、最大值和平均值聚合始终返回 1。Minimum, maximum, and average aggregations always return 1. 有关详细信息，请参阅支持的聚合。For more information, see Supported aggregations.

事件网格指标Event grid metrics

对于“计价单位”值为“计数”的指标，只有总计（总和）聚合有效 。For metrics with a Unit value of Count, only total (sum) aggregation is valid. 最小值、最大值和平均值聚合始终返回 1。Minimum, maximum, and average aggregations always return 1. 有关详细信息，请参阅支持的聚合。For more information, see Supported aggregations.

作业指标Jobs metrics

对于“计价单位”值为“计数”的指标，只有总计（总和）聚合有效 。For metrics with a Unit value of Count, only total (sum) aggregation is valid. 最小值、最大值和平均值聚合始终返回 1。Minimum, maximum, and average aggregations always return 1. 有关详细信息，请参阅支持的聚合。For more information, see Supported aggregations.

路由指标Routing metrics

对于“计价单位”值为“计数”的指标，只有总计（总和）聚合有效 。For metrics with a Unit value of Count, only total (sum) aggregation is valid. 最小值、最大值和平均值聚合始终返回 1。Minimum, maximum, and average aggregations always return 1. 有关详细信息，请参阅支持的聚合。For more information, see Supported aggregations.

孪生查询指标Twin query metrics

对于“计价单位”值为“计数”的指标，只有总计（总和）聚合有效 。For metrics with a Unit value of Count, only total (sum) aggregation is valid. 最小值、最大值和平均值聚合始终返回 1。Minimum, maximum, and average aggregations always return 1. 有关详细信息，请参阅支持的聚合。For more information, see Supported aggregations.

指标维度Metric dimensions

Azure IoT 中心具有以下与它的一些路由和事件网格指标关联的维度。Azure IoT Hub has the following dimensions associated with some of its routing and event grid metrics.

若要了解有关指标维度的详细信息，请参阅多维指标。To learn more about metric dimensions, see Multi-dimensional metrics.

资源日志Resource logs

本节列出为 Azure IoT 中心收集的所有资源日志类别类型和架构。This section lists all the resource log category types and schemas collected for Azure IoT Hub. 所有 IoT 中心日志的资源提供程序和类型均为 Microsoft.Devices/IotHubs。The resource provider and type for all IoT Hub logs is Microsoft.Devices/IotHubs.

本节主题Topics in this section

• 连接Connections
• 设备遥测Device telemetry
• 云到设备的命令Cloud-to-device commands
• 设备标识操作Device identity operations
• 文件上传操作File upload operations
• RoutesRoutes
• 设备到云孪生操作Device-to-cloud twin operations
• 云到设备孪生操作Cloud-to-device twin operations
• 孪生查询Twin queries
• 作业操作Jobs operations
• 直接方法Direct Methods
• 分布式跟踪（预览版）Distributed Tracing (Preview)
  • IoT 中心 D2C（设备到云）日志IoT Hub D2C (device-to-cloud) logs
  • IoT 中心流入日志IoT Hub ingress logs
  • IoT 中心流出日志IoT Hub egress logs
• 配置Configurations
• 设备流（预览版）Device Streams (Preview)

连接Connections

连接类别跟踪设备连接，并断开事件与 IoT 中心和错误的连接。The connections category tracks device connect and disconnect events from an IoT hub as well as errors. 此类别用于识别未经授权的连接尝试或者在失去与设备的连接时发出警报。This category is useful for identifying unauthorized connection attempts and or alerting when you lose connection to devices.

{
   "records":
   [
        {
            "time": " UTC timestamp",
            "resourceId": "Resource Id",
            "operationName": "deviceConnect",
            "category": "Connections",
            "level": "Information",
            "properties": "{\"deviceId\":\"<deviceId>\",\"sdkVersion\":\"<sdkVersion>\",\"protocol\":\"<protocol>\",\"authType\":\"{\\\"scope\\\":\\\"device\\\",\\\"type\\\":\\\"sas\\\",\\\"issuer\\\":\\\"iothub\\\",\\\"acceptingIpFilterRule\\\":null}\",\"maskedIpAddress\":\"<maskedIpAddress>\"}",
            "location": "Resource location"
        }
    ]
}

设备遥测Device telemetry

设备遥测类别跟踪在 IoT 中心发生且与遥测管道相关的错误。The device telemetry category tracks errors that occur at the IoT hub and are related to the telemetry pipeline. 此类别包括发送遥测事件（例如限制）和接收遥测事件（例如未经授权的读取者）时发生的错误。This category includes errors that occur when sending telemetry events (such as throttling) and receiving telemetry events (such as unauthorized reader). 此类别无法捕捉设备本身运行的代码所造成的错误。This category cannot catch errors caused by code running on the device itself.

{
    "records":
    [
        {
            "time": "UTC timestamp",
            "resourceId": "Resource Id",
            "operationName": "ingress",
            "category": "DeviceTelemetry",
            "level": "Error",
            "resultType": "Event status",
            "resultDescription": "MessageDescription",
            "properties": "{\"deviceId\":\"<deviceId>\",\"batching\":\"0\",\"messageSizeInBytes\":\"<messageSizeInBytes>\",\"EventProcessedUtcTime\":\"<UTC timestamp>\",\"EventEnqueuedUtcTime\":\"<UTC timestamp>\",\"partitionId\":\"1\"}", 
            "location": "Resource location"
        }
    ]
}

云到设备的命令Cloud-to-device commands

云到设备的命令类别跟踪在 IoT 中心发生且与云到设备的消息管道相关的错误。The cloud-to-device commands category tracks errors that occur at the IoT hub and are related to the cloud-to-device message pipeline. 此类别包括在以下情况下发生的错误：This category includes errors that occur from:

• 发送云到设备消息时（例如“未经授权的发件人”错误），Sending cloud-to-device messages (like unauthorized sender errors),
• 接收云到设备消息时（例如“超出传递计数”错误），以及Receiving cloud-to-device messages (like delivery count exceeded errors), and
• 接收云到设备消息反馈时（例如“反馈已过期”错误）。Receiving cloud-to-device message feedback (like feedback expired errors).

此类别不捕捉当云到设备消息已成功传递但设备未正确进行处理时出现的错误。This category does not catch errors when the cloud-to-device message is delivered successfully but then improperly handled by the device.

{
    "records":
    [
        {
            "time": " UTC timestamp",
            "resourceId": "Resource Id",
            "operationName": "messageExpired",
            "category": "C2DCommands",
            "level": "Error",
            "resultType": "Event status",
            "resultDescription": "MessageDescription",
            "properties": "{\"deviceId\":\"<deviceId>\",\"messageId\":\"<messageId>\",\"messageSizeInBytes\":\"<messageSize>\",\"protocol\":\"Amqp\",\"deliveryAcknowledgement\":\"<None, NegativeOnly, PositiveOnly, Full>\",\"deliveryCount\":\"0\",\"expiryTime\":\"<timestamp>\",\"timeInSystem\":\"<timeInSystem>\",\"ttl\":<ttl>, \"EventProcessedUtcTime\":\"<UTC timestamp>\",\"EventEnqueuedUtcTime\":\"<UTC timestamp>\", \"maskedIpAddress\": \"<maskedIpAddress>\", \"statusCode\": \"4XX\"}",
            "location": "Resource location"
        }
    ]
}

设备标识操作Device identity operations

设备标识操作类别跟踪你尝试在其 IoT 中心的标识注册表中创建、更新或删除条目时所发生的错误。The device identity operations category tracks errors that occur when you attempt to create, update, or delete an entry in your IoT hub's identity registry. 预配方案就很适合跟踪此类别。Tracking this category is useful for provisioning scenarios.

{
    "records":
    [
        {
            "time": "UTC timestamp",
            "resourceId": "Resource Id",
            "operationName": "get",
            "category": "DeviceIdentityOperations",
            "level": "Error",
            "resultType": "Event status",
            "resultDescription": "MessageDescription",
            "properties": "{\"maskedIpAddress\":\"<maskedIpAddress>\",\"deviceId\":\"<deviceId>\", \"statusCode\":\"4XX\"}",
            "location": "Resource location"
        }
    ]
}

文件上传操作File upload operations

文件上传类别跟踪在 IoT 中心发生且与文件上传功能相关的错误。The file upload category tracks errors that occur at the IoT hub and are related to file upload functionality. 此类别包括：This category includes:

• SAS URI 发生的错误，例如它在设备就上传完毕通知中心之前到期。Errors that occur with the SAS URI, such as when it expires before a device notifies the hub of a completed upload.

• 设备报告的失败上传。Failed uploads reported by the device.

• 创建 IoT 中心通知消息期间在存储中找不到文件时发生的错误。Errors that occur when a file is not found in storage during IoT Hub notification message creation.

此类别不能捕获在设备将文件上传到存储时直接发生的错误。This category cannot catch errors that directly occur while the device is uploading a file to storage.

{
    "records":
    [
        {
            "time": "UTC timestamp",
            "resourceId": "Resource Id",
            "operationName": "ingress",
            "category": "FileUploadOperations",
            "level": "Error",
            "resultType": "Event status",
            "resultDescription": "MessageDescription",
            "durationMs": "1",
            "properties": "{\"deviceId\":\"<deviceId>\",\"protocol\":\"<protocol>\",\"authType\":\"{\\\"scope\\\":\\\"device\\\",\\\"type\\\":\\\"sas\\\",\\\"issuer\\\":\\\"iothub\\\",\\\"acceptingIpFilterRule\\\":null}\",\"blobUri\":\"http//bloburi.com\"}",
            "location": "Resource location"
        }
    ]
}

路由Routes

消息路由类别跟踪消息路由评估期间发生的错误以及 IoT 中心感知到的终结点运行状况。The message routing category tracks errors that occur during message route evaluation and endpoint health as perceived by IoT Hub. 此类别包括诸如下列项的事件：This category includes events such as:

• 规则评估结果为“未定义”，A rule evaluates to "undefined",
• IoT 中心将某个终结点标记为死终结点，或者IoT Hub marks an endpoint as dead, or
• 从终结点收到的任何错误。Any errors received from an endpoint.

此类别不包含有关消息本身的特定错误（例如设备限制错误），这些错误在“设备遥测”类别下报告。This category does not include specific errors about the messages themselves (like device throttling errors), which are reported under the "device telemetry" category.

{
    "records":
    [
        {
            "time":"2019-12-12T03:25:14Z",
            "resourceId":"/SUBSCRIPTIONS/91R34780-3DEC-123A-BE2A-213B5500DFF0/RESOURCEGROUPS/ANON-TEST/PROVIDERS/MICROSOFT.DEVICES/IOTHUBS/ANONHUB1",
            "operationName":"endpointUnhealthy",
            "category":"Routes",
            "level":"Error",
            "resultType":"403004",
            "resultDescription":"DeviceMaximumQueueDepthExceeded",
            "properties":"{\"deviceId\":null,\"endpointName\":\"anon-sb-1\",\"messageId\":null,\"details\":\"DeviceMaximumQueueDepthExceeded\",\"routeName\":null,\"statusCode\":\"403\"}",
            "location":"chinaeast"
        }
    ]
}

以下是有关路由资源日志的更多详细信息：Here are more details on routing resource logs:

• 路由资源日志错误代码列表List of routing resource log error codes
• 路由资源日志操作名称列表List of routing resource logs operationNames

设备到云孪生操作Device-to-cloud twin operations

设备到云孪生操作类别跟踪设备孪生上设备发起的事件。The device-to-cloud twin operations category tracks device-initiated events on device twins. 这些操作可能包括获取孪生、更新报告属性和订阅所需属性。These operations can include get twin, update reported properties, and subscribe to desired properties.

{
    "records":
    [
        {
            "time": "UTC timestamp",
            "resourceId": "Resource Id",
            "operationName": "update",
            "category": "D2CTwinOperations",
            "level": "Information",
            "durationMs": "1",
            "properties": "{\"deviceId\":\"<deviceId>\",\"protocol\":\"<protocol>\",\"authenticationType\":\"{\\\"scope\\\":\\\"device\\\",\\\"type\\\":\\\"sas\\\",\\\"issuer\\\":\\\"iothub\\\",\\\"acceptingIpFilterRule\\\":null}\"}",
            "location": "Resource location"
        }
    ]
}

云到设备孪生操作Cloud-to-device twin operations

云到设备孪生操作类别跟踪设备孪生上服务发起的事件。The cloud-to-device twin operations category tracks service-initiated events on device twins. 这些操作可能获取孪生、更新或替换标记，以及更新或替换所需属性。These operations can include get twin, update or replace tags, and update or replace desired properties.

{
    "records":
    [
        {
            "time": "UTC timestamp",
            "resourceId": "Resource Id",
            "operationName": "read",
            "category": "C2DTwinOperations",
            "level": "Information",
            "durationMs": "1",
            "properties": "{\"deviceId\":\"<deviceId>\",\"sdkVersion\":\"<sdkVersion>\",\"messageSize\":\"<messageSize>\"}",
            "location": "Resource location"
        }
    ]
}

孪生查询Twin queries

孪生查询类别报告在云中针对设备孪生发起的查询请求。The twin queries category reports on query requests for device twins that are initiated in the cloud.

{
    "records":
    [
        {
            "time": "UTC timestamp",
            "resourceId": "Resource Id",
            "operationName": "query",
            "category": "TwinQueries",
            "level": "Information",
            "durationMs": "1",
            "properties": "{\"query\":\"<twin query>\",\"sdkVersion\":\"<sdkVersion>\",\"messageSize\":\"<messageSize>\",\"pageSize\":\"<pageSize>\", \"continuation\":\"<true, false>\", \"resultSize\":\"<resultSize>\"}",
            "location": "Resource location"
        }
    ]
}

作业操作Jobs operations

作业操作类别报告在多个设备上更新设备孪生或调用直接方法的作业请求。The jobs operations category reports on job requests to update device twins or invoke direct methods on multiple devices. 这些请求在云中发起。These requests are initiated in the cloud.

{
    "records":
    [
        {
            "time": "UTC timestamp",
            "resourceId": "Resource Id",
            "operationName": "jobCompleted",
            "category": "JobsOperations",
            "level": "Information",
            "durationMs": "1",
            "properties": "{\"jobId\":\"<jobId>\", \"sdkVersion\": \"<sdkVersion>\",\"messageSize\": <messageSize>,\"filter\":\"DeviceId IN ['1414ded9-b445-414d-89b9-e48e8c6285d5']\",\"startTimeUtc\":\"Wednesday, September 13, 2017\",\"duration\":\"0\"}",
            "location": "Resource location"
        }
    ]
}

直接方法Direct Methods

直接方法类别跟踪发送到单个设备的请求-响应交互。The direct methods category tracks request-response interactions sent to individual devices. 这些请求在云中发起。These requests are initiated in the cloud.

{
    "records":
    [
        {
            "time": "UTC timestamp",
            "resourceId": "Resource Id",
            "operationName": "send",
            "category": "DirectMethods",
            "level": "Information",
            "durationMs": "1",
            "properties": "{\"deviceId\":<messageSize>, \"RequestSize\": 1, \"ResponseSize\": 1, \"sdkVersion\": \"2017-07-11\"}",
            "location": "Resource location"
        }
    ]
}

配置Configurations

IoT 中心配置日志跟踪有关自动设备管理功能集的事件和错误。IoT Hub configuration logs track events and error for the Automatic Device Management feature set.

{
    "records":
    [
         {
             "time": "2019-09-24T17:21:52Z",
             "resourceId": "Resource Id",
             "operationName": "ReadManyConfigurations",
             "category": "Configurations",
             "resultType": "",
             "resultDescription": "",
             "level": "Information",
             "durationMs": "17",
             "properties": "{\"configurationId\":\"\",\"sdkVersion\":\"2018-06-30\",\"messageSize\":\"0\",\"statusCode\":null}",
             "location": "southcentralus"
         }
    ]
}

设备流（预览版）Device Streams (Preview)

设备流类别跟踪发送到单个设备的请求-响应交互。The device streams category tracks request-response interactions sent to individual devices.

{
    "records":
    [
         {
             "time": "2019-09-19T11:12:04Z",
             "resourceId": "Resource Id",
             "operationName": "invoke",
             "category": "DeviceStreams",
             "resultType": "",
             "resultDescription": "",    
             "level": "Information",
             "durationMs": "74",
             "properties": "{\"deviceId\":\"myDevice\",\"moduleId\":\"myModule\",\"sdkVersion\":\"2019-05-01-preview\",\"requestSize\":\"3\",\"responseSize\":\"5\",\"statusCode\":null,\"requestName\":\"myRequest\",\"direction\":\"c2d\"}",
             "location": "Central US"
         }
    ]
}

Azure Monitor 日志表Azure Monitor Logs tables

本节介绍与 Azure IoT 中心相关并可通过 Log Analytics 进行查询的所有 Azure Monitor 日志 Kusto 表。This section refers to all of the Azure Monitor Logs Kusto tables relevant to Azure IoT Hub and available for query by Log Analytics. 有关这些表的列表以及指向 IoT 中心资源类型的详细信息的链接，请参阅 Azure Monitor 日志表参考中的 IoT 中心。For a list of these tables and links to more information for the IoT Hub resource type, see IoT Hub in the Azure Monitor Logs table reference.

有关所有 Azure Monitor 日志/Log Analytics 表的参考，请参阅 Azure Monitor 日志表参考。For a reference of all Azure Monitor Logs / Log Analytics tables, see the Azure Monitor Log Table Reference.

另请参阅See Also

• 有关监视 Azure IoT 中心的说明，请参阅监视 Azure IoT 中心。See Monitor Azure IoT Hub for a description of monitoring Azure IoT Hub.
• 有关监视 Azure 资源的详细信息，请参阅使用 Azure Monitor 监视 Azure 资源。See Monitoring Azure resources with Azure Monitor for details on monitoring Azure resources.