Cloud Run + gRPC Endpoints service use reporting

[Dan Massey]

Hi there,

I have a gRPC service deployed to fully managed Cloud Run, with the ESPv2 proxy deployed as a separate Cloud Run service.

Thanks to help from this group, transcoding to JSON and access permissions are working correctly.

However, in the Endpoints UI in Cloud Console all of the usage data (requests/second, errors, latency) reports as 0. In the Cloud Run section of console, the non-zero requests/second value shows.

Any advice on how to troubleshoot or debug would be greatly appreciated.

Thanks

Dan 

[Teju Nareddy]

Hi Dan, thanks for reporting this issue.

Does this only occur for gRPC requests, or also HTTP requests that are transcoded to gRPC? I have previously tested that transcoded requests will show up in the UI. I will double-check for gRPC requests later today.

If you're not even seeing transcoded requests in the UI, then perhaps you forgot to enable your endpoints service?

Using this command: `gcloud enable ENDPOINTS_SERVICE_NAME`

[Dan Massey]

Thanks Teju.

This was for all requests -- seems like enabling the endpoints service was to blame.

Is there any documentation that explains what each of these does:

gcloud services enable servicemanagement.googleapis.com
gcloud services enable servicecontrol.googleapis.com
gcloud services enable endpoints.googleapis.com
gcloud services enable ENDPOINTS_SERVICE_NAME

I'm a bit confused how the API was functioning (seemingly) correctly without having those services enabled.

Thanks

Dan

--
You received this message because you are subscribed to the Google Groups "Google Cloud Endpoints" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-cloud-endp...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-endpoints/7090716a-4cc1-4101-8ac4-325c507ae172%40googlegroups.com.

--

Dan Massey

Product, Engineering & Data

(415) 890-4117

nomnomnow.com

Instagram | Facebook | Twitter

[Teju Nareddy]

No problem, glad it is working.

I am not aware of any consolidated documentation, but you can find out more about the first 3 on the Google API Explorer.

The last one (ENDPOINTS_SERVICE_NAME) is similar to servicecontrol.googleapis.com, but specifically for each endpoint service you deploy.

> I'm a bit confused how the API was functioning (seemingly) correctly without having those services enabled.

This is actually somewhat working as intended. In the case of a control plane outage in GCP, we still want your API traffic to reach your backend (even if you miss out on some metrics in the UI). We are brainstorming ways to distinguish between a configuration error and an outage, so we can surface config errors.