Description of problem:{code:none}

Using the (unsupported) dynamicConfigManager  feature of OpenShift Router, we notice that whilst routes that have been statically defined in the haproxy.config operator correctly report prometheus metrics, those which take the dynamic path, fail to report metrics.

4.11.25

100%

1. Create an ingresscontrollers.operator.openshift.io resource with {{dynamicConfigManager: "true"}}
2. Create a TLS passthrough {{routes.route.openshift.io}} resource exposing a TLS service
3. Send traffic to the route

Observe the platform metrics for {{haproxy_backend_bytes_out_total}} and {{haproxy_backend_bytes_in_total}}.  The reported bytes in/bytes out are zero.

Metrics faithfully report bytes in/out, even for routes that follow the dynamic path.