Get Blob Service Stats¶
The Get Blob Service Stats operation retrieves statistics related to replication for the Blob service. It is only available on the secondary location endpoint when read-access geo-redundant replication is enabled for the storage account.
Although CORS rules are listed in this schema, Blobserver 1.2.1 does not support CORS features.
The Get Blob Service Stats request may be constructed as follows. HTTPS is
-secondary suffix is required when you replace
myaccount with the name of your storage account. Replace example.com with
your endpoint’s domain name or IP address.
|Method||Request URI||HTTP Version|
The URI must always include the forward slash (/) to separate the host name from the path and query portions of the URI. In the case of this operation, the path portion of the URI is empty.
The following additional parameters may be specified on the request URI.
The following table describes required and optional request headers.
||Required. Specifies the authorization scheme, account name, and signature. For more information, see Authorize requests to Azure Storage.|
||Required. Specifies the Coordinated Universal Time (UTC) for the request. For more information, see Authorize requests to Azure Storage.|
||Required for all authorized requests. Specifies the version of the operation to use for this request. For more information, see Versioning for the Azure Storage services.|
||Optional. Client generated opaque value with 1KB character limit that is recorded in the analytics logs when Storage Analytics Logging is enabled. This header is recommended for correlating client side activities with requests received by the server. For more information see Windows Azure Logging: Using Logs to Track Storage Requests.|
The response includes an HTTP status code, a set of response headers, and a response body.
A successful operation returns status code 200 (OK). When called on secondary
location endpoint that is not enabled for secondary read, it returns an
HTTP status code of 403 with
The response for this operation includes the following headers. The response also includes additional standard HTTP headers. All standard headers conform to the HTTP/1.1 protocol specification.
||This header uniquely identifies the request that was made and can be used for troubleshooting the request. For more information, see Troubleshooting API operations.|
||Specifies the version of the operation used for the response. For more information, see Versioning for the Azure Storage services.|
||A UTC date/time value generated by the service that indicates the time at which the response was initiated.|
||This header can be used to troubleshoot requests and
corresponding responses. The value of this header is
equal to the value of the
The format of the response body is as follows:
<?xml version="1.0" encoding="utf-8"?> <StorageServiceStats> <GeoReplication> <Status>live|bootstrap|unavailable</Status> <LastSyncTime>sync-time|<empty></LastSyncTime> </GeoReplication> </StorageServiceStats>
The following table describes the elements of the response body:
The status of the secondary location. Possible values are:
||A GMT date/time value, to the
second. All primary writes
preceding this value are
guaranteed to be available for
read operations at the secondary.
Primary writes after this point
in time may or may not be
available for reads.
The value may be empty if
With geo-redundant replication, Azure Storage maintains your data durable in two locations. In both locations, Azure Storage constantly maintains multiple healthy replicas of your data.
The location where you read, create, update, or delete data is the primary storage account location. The primary location exists in the region you choose at the time you create an account via the Azure Management Azure classic portal, for example, “North Central US”. The location to which your data is replicated is the secondary location. The secondary location resides in a region that is automatically geographically paired with the primary region. Read-only access is available from the secondary location, if read-access geo-redundant replication is enabled for your storage account. For more on read-access geo-redundant replication, see Windows Azure Storage Redundancy Options and Read Access Geo Redundant Storage.
To construct a request for a read operation against the secondary endpoint, append
-secondaryas a suffix to the account name in the URI that you use to read from Blob storage. For example, a secondary URI for the Get Blob operation will be similar to
Sample Request and Response¶
The following is a sample request for the
Get Blob Service Stats operation:
GET http://myaccount-secondary.blob.example.com/?restype=service&comp=stats HTTP/1.1
The request is sent with following headers:
x-ms-version: 2013-08-15 x-ms-date: Wed, 23 Oct 2013 22:08:44 GMT Authorization: SharedKey myaccount:CY1OP3O3jGFpYFbTCBimLn0Xov0vt0khH/E5Gy0fXvg=
The status code and response headers are returned as follows:
HTTP/1.1 200 OK Content-Type: application/xml Date: Wed, 23 Oct 2013 22:08:54 GMT x-ms-version: 2013-08-15 x-ms-request-id: cb939a31-0cc6-49bb-9fe5-3327691f2a30 Server: Windows-Azure-Blob/1.0 Microsoft-HTTPAPI/2.0
The response includes the following XML body:
<?xml version="1.0" encoding="utf-8"?> <StorageServiceStats> <GeoReplication> <Status>live</Status> <LastSyncTime> Wed, 23 Oct 2013 22:05:54 GMT</LastSyncTime> </GeoReplication> </StorageServiceStats>