We have a proxy that logs to google cloud when a fault occurs. This proxy also calls a shared flow, where shared flow has a service callout to publish to a topic. In google cloud logs, the proxy has 503 and 502 errors, but in API Monitoring there are no metrics for it. Has anyone encountered something like this? Trying to figure out if its better to update the proxy to have its own service callout.
@rhona - this is interesting and have not seen this. Would it be possible for you to try it out? I mean create a proxy that does a service callout to a service say https://httpbin.org/status/503 and then see if API Monitoring is capturing those failures. It could be possible that its not capturing failures happening in the SharedFlow. Appreciate if you can try that
We found that the api metrics > error code analysis tab shows the 5xx error count
But we couldn't figure out this table in Api Monitoring.
In Api Metrics we have two 502, and three 503 on the same day