When APIcast Camel Policy is configured, the upstream_status and upstream_response_time for the service are not shown. This occurs on both 200 and 500 errors from API backend. From an application perspective ( customer's expectation) the upstream_response_time and upstream_status should be set regardless of whether or not Camel Proxy is being used.

If APIcast Camel Policy is not used, the same 2 metrics are set. This can be observed by fetching the metrics from APIcast 

$ oc rsh {apicast-pod} curl http://localhost:9421/metrics

output
upstream_status{status="500",service_id="...",service_system_name="..."} 3
upstream_response_time_seconds_sum{service_id="...",service_system_name="..."} 0.xxx

Whether the APIcast Camel Policy is used or not, apicast_status for the status code (200, 500) is always incremented. For e.g.

apicast_status{status="500"} 3
apicast_status{status="200"} 5

The attached files show the metrics for 200 and 500 errors as described above. Some files may show the metrics and after the test have been performed.