Open erhan-talarian opened 2 years ago
This means Google's service control
service is down(503). How often do you see it? Is it good now?
I checked the logs from last 14 days and 9 of them has occurrences of this error. Minimum is 1 error per day and max is 65 errors per day (API average is 3 requests / sec). Normally I wouldn't be bothered but I suspect some requests somehow never reach the App Engine application (no logs/errors) and API GW responds with HTTP 500 (sometimes 502) directly, that's why I am a little bit concerned.
For the errors with path = "/v1/services/abc.apigateway.abc.cloud.goog:report", these are less severe than path = "/v1/services/abc.apigateway.abc.cloud.goog:check". The former is called at the end of requests,to send telemetry info, their failures cause the request data not showing in the graph, not showing access logs.
The latter is for checking access control, such as api-key, their failures may reject the requests and cause the requests not reaching to your app-engine applications, could you check to see if there are such errors.
The error for failing calling /v1/services/abc.apigateway.abc.cloud.goog:report
happens on log path not request path which won't effect your service availability, so it shouldn't some other problems if the requests are not forwarded to your backend.
The SLO for report is 99.9%. I think 65 per day for 3QPS looks good to me.
There are also errors for "/v1/services/abc.apigateway.abc.cloud.goog:check", but less frequent (3 days out of last 14, max 17 errors/day). However, the timings for these errors don't match the requests I suspect of not reaching App Engine, so I guess they are "innocent".
Hi, I have an App Engine Standard Java 11 application served behind a GCP API Gateway. When I check the Cloud Logs I frequently see these errors like the following from API Gateway:
What do these errors mean, should I be concerned?
Thank you