Score:0

Unable to identify which quota is being exceeded from error logs

us flag

During increased traffic my API which runs on Cloud Run gives the error copied below. My best guess is that this is due to some Cloud Datastore call since any calls to this Cloud Run instance which does not use Datastore does not give this error during the "outage". Unfortunately there is no indication of which quota gets exceeded I have looked through my quotas and cannot see anything that is peeking (see quota usage screenshot). How can I trace down which quota is causing the issue?

error: {
    code: 8
    details: "Quota exceeded."
    note: "Exception occurred in retry method that was not classified as transient"
}
stack: "Error: 8 RESOURCE_EXHAUSTED: Quota exceeded.
    at Object.callErrorFromStatus (/usr/app/node_modules/@grpc/grpc-js/build/src/call.js:31:26)
    at Object.onReceiveStatus (/usr/app/node_modules/@grpc/grpc-js/build/src/client.js:180:52)
    at Object.onReceiveStatus (/usr/app/node_modules/@grpc/grpc-js/build/src/client-interceptors.js:336:141)
    at Object.onReceiveStatus (/usr/app/node_modules/@grpc/grpc-js/build/src/client-interceptors.js:299:181)
    at /usr/app/node_modules/@grpc/grpc-js/build/src/call-stream.js:160:78
    at processTicksAndRejections (internal/process/task_queues.js:79:11)"
mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.