Supported metrics for Microsoft.HealthcareApis/workspaces/fhirservices

The following table lists the metrics available for the Microsoft.HealthcareApis/workspaces/fhirservices 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/workspaces/fhirservices

Category: Availability

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

The availability rate of the service.
Availability Percent Average <none> PT1M Yes

Category: Errors

Metric Name in REST API Unit Aggregation Dimensions Time Grains DS Export
Total Errors

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

Category: Saturation

Metric Name in REST API Unit Aggregation Dimensions Time Grains DS Export
Total Data Size

Total size of the data in the backing database, in bytes.
TotalDataSize Bytes Total (Sum) <none> PT1M Yes

Category: Traffic

Metric Name in REST API Unit Aggregation Dimensions Time Grains DS Export
Total Latency

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

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

Next steps