Hi @崔 演友 ,
Thanks for your patience.
For Internal Server Error it could be the capacity constraint which is of temporary nature.
ERROR: [{'code':'InternalServerError','message':'An unexpected error occured while processing the request. Tracking ID: '9b9bfce3-f590-49af-90e1-a777596e5373''}]}
Replace Timestamp, Subscription ID, Correlation ID or ServiceRequestID (Tracking ID from the Error message) and get the ASYNCID from the below queries
(HttpOutgoingRequests and HttpIncomingRequests needs to be accessed from ARMProd)
/Get ASYNC ID from the below - Replace Timestamp, Subscription ID, Correlation ID and get the asyncId from the below query.
HttpOutgoingRequests
| where (TIMESTAMP >= datetime(2021-07-07T20:45:58Z) and TIMESTAMP < datetime(2021-07-07T21:10:58Z))
| where subscriptionId =~ "customersubscriptionid"
| where serviceRequestId =~ '9b9bfce3-f590-49af-90e1-a777596e5373' //Tracking ID from Customer
//| where correlationId =~ "ab1ac73d-ed79-4650-8bb3-ffa29dbbaf45"
| where operationName contains "AZUREASYNCOPERATION"
| extend location = extract('locations/([a-z|A-Z|0-9|]+)', 1, targetUri, typeof(string))
| extend asyncId = extract('azureAsyncOperation/([a-z|A-Z|0-9|-]+)', 1, targetUri, typeof(string))
| where isnotempty( asyncId) //and location contains "AddRegionHere"
| project TIMESTAMP, correlationId, asyncId,TaskName, location, subscriptionId, operationName, targetUri, durationInMilliseconds,httpStatusCode,clientRequestId, exceptionMessage, errorCode, errorMessage
You can get the same information from below query also.
//Get ASYNC ID from the below - Replace Timestamp, Subscription ID, Correlation ID and get the asyncId from the below query.
HttpIncomingRequests
| where (TIMESTAMP >= datetime(2021-07-07T20:45:58Z) and TIMESTAMP < datetime(2021-07-07T21:10:58Z))
| where subscriptionId =~ "customersubscriptionid"
| where serviceRequestId =~ '9b9bfce3-f590-49af-90e1-a777596e5373' //Tracking ID from Customer
//| where correlationId =~ "ab1ac73d-ed79-4650-8bb3-ffa29dbbaf45"
| where operationName contains "AZUREASYNCOPERATION"
| extend location = extract('locations/([a-z|A-Z|0-9|]+)', 1, targetUri, typeof(string))
| extend asyncId = extract('azureAsyncOperation/([a-z|A-Z|0-9|-]+)', 1, targetUri, typeof(string))
| where isnotempty( asyncId) //and location contains "AddRegionHere"
| project TIMESTAMP, correlationId, asyncId, location,TaskName, subscriptionId, operationName, targetUri, durationInMilliseconds,httpStatusCode,clientRequestId, exceptionMessage, errorCode, errorMessage
Provide the ASYNC ID from the step 1 in the below query in request_id column to find the operation parameters to get the details about the operation
//Get the Operational Parameters for the server creation
MonOrcasBreadthRp
| where TIMESTAMP > ago(7d)
| where request_id =~ "838f778d-602e-4614-8066-f75487480f7c"
| where operation_parameters !=''
| project TIMESTAMP, operation_parameters
Using the query below you can find the exception messages. This query is helpful when investigating Capacity constraint issues.
/Get the Error messages
MonOrcasBreadthRpExceptions
| where (TIMESTAMP >= datetime(2021-07-07T20:45:58Z) and TIMESTAMP < datetime(2021-07-07T21:10:58Z))
| where request_id =~ "f3b85aaf-8c21-4e8e-93d1-a5a251f7614a"
//| where message !contains "Finite State Machine [OrcasResourceSpecificationCreateOperation] with key" and message !contains "doesn\'t exist in the backing store"
| project TIMESTAMP, event, exception_type, message, stack_trace, level
It could be the region is constrained due to capacity temporarily.
Hope this helps, please let us in case of further queries.