You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Based on a recent incident, we wanted to know how feasible it would be to include the container that they are trying to access in the diagnostic logs. User is setting "endpoint" but receiving and error "Server could not parse the Url" but since we are not able to see what that actual value is, we want to include it in the diagnostics.
Reference:
return new CosmosClientBuilder()
.endpoint(uri)
.credential(azureKeyCredential)
.directMode(directConnectionConfig, gatewayConnectionConfig);
The text was updated successfully, but these errors were encountered:
Based on a recent incident, we wanted to know how feasible it would be to include the container that they are trying to access in the diagnostic logs. User is setting "endpoint" but receiving and error "Server could not parse the Url" but since we are not able to see what that actual value is, we want to include it in the diagnostics.
Reference:
return new CosmosClientBuilder()
.endpoint(uri)
.credential(azureKeyCredential)
.directMode(directConnectionConfig, gatewayConnectionConfig);
The text was updated successfully, but these errors were encountered: