We've been using Cosmonaut for a while and recently we got it deployed under some heavy load on PROD.
We seem to be getting a few weird exceptions for some of the document Ids see below.
Already checked the Ids and they don't seem to contain any weird characters or anything.
Do you have any input on why this might be happening?
{
"Error":{
"code":"Unauthorized",
"message":"The input authorization token can't serve the request. Please check that the expected payload is built as per the protocol, and check the key being used. Server used the following payload to sign: 'get\ndocs\ndbs/chargestation/colls/cpi/docs/ENGIE_A000063\nfri, 15 may 2020 08:50:26 gmt\n\n'\r\nActivityId: e83fd72c-3fcd-43ad-a99a-1fa4fff5169f, Microsoft.Azure.Documents.Common/2.11.0",
"_ts":0
},
"ActivityId":"e83fd72c-3fcd-43ad-a99a-1fa4fff5169f",
"RetryAfter":"00:00:00",
"ResponseHeaders":[
"Transfer-Encoding",
"Server",
"x-ms-activity-id",
"Strict-Transport-Security",
"x-ms-gatewayversion",
"Date"
],
"StatusCode":401,
"RequestCharge":0.0,
"Message":"The input authorization token can't serve the request. Please check that the expected payload is built as per the protocol, and check the key being used. Server used the following payload to sign: 'get\ndocs\ndbs/chargestation/colls/cpi/docs/ENGIE_A000063\nfri, 15 may 2020 08:50:26 gmt\n\n'\r\nActivityId: e83fd72c-3fcd-43ad-a99a-1fa4fff5169f, Microsoft.Azure.Documents.Common/2.11.0, Windows/10.0.14393 documentdb-netcore-sdk/2.4.0",
"StackTrace":" at Cosmonaut.Extensions.ExceptionHandlingExtensions.DocumentClientExceptionToCosmosResponse[TEntity](DocumentClientException exception, TEntity entity)\r\n at Cosmonaut.Extensions.ExceptionHandlingExtensions.ToCosmosResponse[TEntity](DocumentClientException exception, TEntity entity)\r\n at Cosmonaut.Extensions.ExceptionHandlingExtensions.ToCosmosResponse[TEntity](DocumentClientException exception)\r\n at Cosmonaut.Extensions.CosmosOperationExtensions.ExecuteCosmosQuery[TResult](Task`1 operationTask)\r\n at Cosmonaut.CosmonautClient.GetDocumentAsync[T](String databaseId, String collectionId, String documentId, RequestOptions requestOptions, CancellationToken cancellationToken)\r\n at Cosmonaut.CosmosStore`1.FindAsync(String id, RequestOptions requestOptions, CancellationToken cancellationToken)\r\n at Gsop.StatusService.Data.CosmosRepositories.ConnectivityStatusCosmosRepository.FindAsync(String id) in d:\\a\\1\\s\\Gsop.StatusService.Data\\CosmosRepositories\\ConnectivityStatusCosmosRepository.cs:line 28\r\n at Gsop.StatusService.Business.StatusService.UpdateLastPduSignalAsync(String message, GcppMessage gcppMessage, Int32 messageType, ChargeStation chargeStation) in d:\\a\\1\\s\\Gsop.StatusService.Business\\StatusService.cs:line 398\r\n at Gsop.StatusService.Functions.Functions.ToGsopMonitor(String message, String messageId, String correlationId, IDictionary`2 userProperties) in d:\\a\\1\\s\\Gsop.StatusService.Functions\\Functions.ServiceBus.cs:line 57",
"Data":{
},
"Source":"Cosmonaut",
"HResult":-2146233088
}
Hi,
We've been using Cosmonaut for a while and recently we got it deployed under some heavy load on PROD.
We seem to be getting a few weird exceptions for some of the document Ids see below. Already checked the Ids and they don't seem to contain any weird characters or anything. Do you have any input on why this might be happening?