Επεξεργασία

Κοινή χρήση μέσω


Supported metrics for Microsoft.HealthcareApis/services

The following table lists the metrics available for the Microsoft.HealthcareApis/services resource type.

Table headings

Metric - The metric display name as it appears in the Azure portal.
Name in Rest API - Metric name as referred to in the REST API.
Unit - Unit of measure.
Aggregation - The default aggregation type. Valid values: Average, Minimum, Maximum, Total, Count.
Dimensions - Dimensions available for the metric.
Time Grains - Intervals at which the metric is sampled. For example, PT1M indicates that the metric is sampled every minute, PT30M every 30 minutes, PT1H every hour, and so on.
DS Export- Whether the metric is exportable to Azure Monitor Logs via Diagnostic Settings.

For information on exporting metrics, see - Metrics export using data collection rules and Create diagnostic settings in Azure Monitor.

For information on metric retention, see Azure Monitor Metrics overview.

For a list of supported logs, see Supported log categories - Microsoft.HealthcareApis/services

Category Metric Name in REST API Unit Aggregation Dimensions Time Grains DS Export
Availability Availability

The availability rate of the service.
Availability Percent Average <none> PT1M Yes
Saturation Cosmos DB Collection Size

The size of the backing Cosmos DB collection, in bytes.
CosmosDbCollectionSize Bytes Total (Sum) <none> PT1M Yes
Saturation Cosmos DB Index Size

The size of the backing Cosmos DB collection's index, in bytes.
CosmosDbIndexSize Bytes Total (Sum) <none> PT1M Yes
Saturation Cosmos DB RU usage

The RU usage of requests to the service's backing Cosmos DB.
CosmosDbRequestCharge Count Total (Sum) Operation, ResourceType PT1M Yes
Traffic Service Cosmos DB requests

The total number of requests made to a service's backing Cosmos DB.
CosmosDbRequests Count Sum Operation, ResourceType PT1M Yes
Saturation Service Cosmos DB throttle rate

The total number of 429 responses from a service's backing Cosmos DB.
CosmosDbThrottleRate Count Sum Operation, ResourceType PT1M Yes
Traffic Number of Incoming Messages

The total number of messages received by the Azure IoT Connector for FHIR prior to any normalization.
IoTConnectorDeviceEvent Count Sum Operation, ConnectorName PT1M Yes
Latency Average Normalize Stage Latency

The average time between an event's ingestion time and the time the event is processed for normalization.
IoTConnectorDeviceEventProcessingLatencyMs Milliseconds Average Operation, ConnectorName PT1M Yes
Traffic Number of Measurements

The number of normalized value readings received by the FHIR conversion stage of the Azure IoT Connector for FHIR.
IoTConnectorMeasurement Count Sum Operation, ConnectorName PT1M Yes
Traffic Number of Message Groups

The total number of unique groupings of measurements across type, device, patient, and configured time period generated by the FHIR conversion stage.
IoTConnectorMeasurementGroup Count Sum Operation, ConnectorName PT1M Yes
Latency Average Group Stage Latency

The time period between when the IoT Connector received the device data and when the data is processed by the FHIR conversion stage.
IoTConnectorMeasurementIngestionLatencyMs Milliseconds Average Operation, ConnectorName PT1M Yes
Traffic Number of Normalized Messages

The total number of mapped normalized values outputted from the normalization stage of the the Azure IoT Connector for FHIR.
IoTConnectorNormalizedEvent Count Sum Operation, ConnectorName PT1M Yes
Errors Total Error Count

The total number of errors logged by the Azure IoT Connector for FHIR
IoTConnectorTotalErrors Count Sum Name, Operation, ErrorType, ErrorSeverity, ConnectorName PT1M Yes
Errors Total Errors

The total number of internal server errors encountered by the service.
TotalErrors Count Sum Protocol, StatusCode, StatusCodeClass, StatusCodeText PT1M Yes
Traffic Total Latency

The response latency of the service.
TotalLatency Milliseconds Average Protocol PT1M Yes
Traffic Total Requests

The total number of requests received by the service.
TotalRequests Count Sum Protocol PT1M Yes

Next steps