UNKNOWN api tag in GCP alerts and monitoring Dashboards

Google Cloud Apigee
1

Hi everyone,

I’m seeing an issue in Apigee alerts and Cloud Monitoring where the proxy name is shown as UNKNOWN.

I have an alert configured to trigger when the error rate of an API increases by 30%. Normally, the alert shows the specific API proxy name, but in some cases I receive an alert where the API name is displayed as UNKNOWN.

I also checked the Monitoring dashboards, and I can see 400 errors attributed to UNKNOWN, instead of a valid proxy name.

This is confusing because my Apigee environment only has around 20–30 API proxies, all with well-defined names, and I’m not aware of any proxy that should appear as UNKNOWN.

Has anyone encountered this before?

  • Under what conditions does Apigee report an API/proxy as UNKNOWN?

  • Could this be related to traffic that doesn’t match a proxy, shared flows, invalid host aliases, or requests rejected before proxy resolution?

Any guidance or explanation would be appreciated.

Thanks in advance!

image
image691×258 9.48 KB

2

Hi @Shahrez_Faisal , I could imagine this is traffic hitting your load balancer and getting to sent to Apigee that doesn’t match any proxy base path, so is just unknown. You could prevent this by filtering only valid paths at the load balancer level.

3

Thank you @tyayers, this is what I was thinking. Probably no base path matches the proxy, so it can’t determine it and shows as UNKNOWN.