Sounds like some parsing of the `req.url` is needed. The advantage of using it as a global middleware is more pragmatic as remembering to add tracking at the event level during the product cycle is so prone to fail IME. This way, you always have some raw data to go back to and can augment it where needed by building out event-level hooks. Because the network request to statsd is so low cost, I've found it advantageous to err on the side of tracking more than is required and then filtering, rather than adding buckets on an ad-hoc basis.