My API presents metrics at the URI /q/metrics. Once the WebAssembly module is configured, the metrics endpoint is no longer available and all the calls by prometheus to the metric end point fail. This in turn makes my API appear unhealthy in Kiali and the service mesh.

I change my ServiceMesh extension to accept the URI /q to avoid the problem but now I hit an obvious problem.

I get an access forbidden error because prometheus is not providing a user_key to the call.

I proved that by calling the /q/metric end point like the following :-

curl http://10.130.1.173:8080/q/metrics?user_key=85ffbea15fea9c34d0cefb59

and that works.

It seems to me that the function of a service running on Openshift and exposing metrics and health status hasn't be considered. It doesn't make sense having to add mappings into the ServiceMeshExtenstion for these endpoints, and I'm not sure if I could even change prometheus to pass a user key.

We should be able to define uri's for health endpoints and metrics and avoid going through the 3scale security checks in the ServiceMesh extension.