I'm trying to get better at debugging Azure issues. Now, I have a log file which says the following:
fail: Microsoft.AspNetCore.DataProtection.KeyManagement.KeyRingProvider[48]
An error occurred while reading the key ring.
Azure.RequestFailedException: This request is not authorized to perform this operation using this permission.
RequestId:2af54d08-xxxx-xxxx-xxxx-f0e0bf000000
Time:2021-12-14T08:49:54.2864189Z
Status: 403 (This request is not authorized to perform this operation using this permission.)
ErrorCode: AuthorizationPermissionMismatch
Headers:
Server: Windows-Azure-Blob/1.0,Microsoft-HTTPAPI/2.0
x-ms-request-id: 2af54d08-xxxx-xxxx-xxxx-f0e0bf000000
x-ms-client-request-id: 5f8d796a-xxxx-xxxx-xxxx-e973903f3201
x-ms-version: 2020-04-08
x-ms-error-code: AuthorizationPermissionMismatch
Date: Tue, 14 Dec 2021 08:49:53 GMT
Content-Length: 279
Content-Type: application/xml
What's always been a bit of a mystery to me are the ids mentioned here. It would be really interesting to look up information on them. For example:
RequestId:2af54d08-xxxx-xxxx-xxxx-f0e0bf000000
x-ms-request-id: 2af54d08-xxxx-xxxx-xxxx-f0e0bf000000
x-ms-client-request-id: 5f8d796a-xxxx-xxxx-xxxx-e973903f3201
Where is the information related to these ids stored?
CodePudding user response:
x-ms-request-id
- Every request made against the storage services returns a response header named
x-ms-request-id
. This header contains an opaque value that uniquely identifies the request.
x-ms-client-request-id
- It is associated with a logical action in the client; e.g. loading the portal monitoring part may have a single client request id for many calls to ARM (e.g. load VMs load metric definitions load metrics)
You can refer to The x-ms-request-id Header, Instrumentation and Tracing across services, Client Request Headers, Azure Corelation Id and Request ID1 and Azure Corelation Id and Request ID2