Challenge:

When using complex custom routes to direct traffic, it is hard to know with certainty which routes are being selected for inbound traffic. This can lead to a fear to touch or modify existing routing policies as there is a risk of disrupting traffic if the route is in use

Proposed solution:

The HTTP request logs (json) should contain an identifier to make it known which routing policy and specifically which route was selected for that request

Benefit:
It becomes easy to see which routes are in use