Stop processing Mapping Rules once the first one is met

If a customer has the following Mapping Rules defined in their API Integration Settings:

(get) /path/to/example/search
(get) /path/to/example/{id}

And distinct Metrics associated to each one.

When calling:

(get) /path/to/example/search

It will result in both metrics being incremented, since it's currently not possible to isolate the String 'search' from a call which could be considered a valid id (e.g. 12345).

On that scenario, it would be useful a flag which, once toggled or checked, would stop processing the remaining Mapping Rules and incrementing their metrics after the first one is met.

In summary, it would be a "stop processing other Mapping Rules" configurable policy through the UI.