Are the calls running in the same service? You can then also try merging the requests by designing a request naming rule that takes out the last /MAC* part in the URL. This will merge the requests. Making it a key requests allows you to create your own anomaly detection on the new requests, therefore the possibility to keep track of a seperate baseline.
This ensure you’ll get an alert of a failure rate increase of all the requests. If the last part is important you’ll need to put the /MAC1-4 in a request attribute so performance per requests is still visible using request filters.