Azure

Azure Client Library Attributes

This section defines generic attributes used by Azure Client Libraries.

AttributeTypeDescriptionExamplesStability
az.namespacestringAzure Resource Provider Namespace as recognized by the client.Microsoft.Storage; Microsoft.KeyVault; Microsoft.ServiceBusDevelopment
az.service_request_idstringThe unique identifier of the service request. It’s generated by the Azure service and returned with the response.00000000-0000-0000-0000-000000000000Development
azure.client.idstringThe unique identifier of the client instance.3ba4827d-4422-483f-b59f-85b74211c11d; storage-client-1Development

Azure Cosmos DB Attributes

This section defines attributes for Azure Cosmos DB.

AttributeTypeDescriptionExamplesStability
azure.cosmosdb.connection.modestringCosmos client connection mode.gateway; directDevelopment
azure.cosmosdb.consistency.levelstringAccount or request consistency level.Eventual; ConsistentPrefix; BoundedStaleness; Strong; SessionDevelopment
azure.cosmosdb.operation.contacted_regionsstring[]List of regions contacted during operation in the order that they were contacted. If there is more than one region listed, it indicates that the operation was performed on multiple regions i.e. cross-regional call. [1]["North Central US", "Australia East", "Australia Southeast"]Development
azure.cosmosdb.operation.request_chargedoubleThe number of request units consumed by the operation.46.18; 1.0Development
azure.cosmosdb.request.body.sizeintRequest payload size in bytes.Development
azure.cosmosdb.response.sub_status_codeintCosmos DB sub status code.1000; 1002Development

[1] azure.cosmosdb.operation.contacted_regions: Region name matches the format of displayName in Azure Location API


azure.cosmosdb.connection.mode has the following list of well-known values. If one of them applies, then the respective value MUST be used; otherwise, a custom value MAY be used.

ValueDescriptionStability
directDirect connection.Development
gatewayGateway (HTTP) connection.Development

azure.cosmosdb.consistency.level has the following list of well-known values. If one of them applies, then the respective value MUST be used; otherwise, a custom value MAY be used.

ValueDescriptionStability
BoundedStalenessbounded_stalenessDevelopment
ConsistentPrefixconsistent_prefixDevelopment
EventualeventualDevelopment
SessionsessionDevelopment
StrongstrongDevelopment