Telemetry GET / POST telemetry data coming up 'undefined' for the path

Not sure how this happened, but it's in the latest release. Likely a regression as a result of the telemetry count work, I can't spot it at first glance.

Another possibility is a change in the order of middleware being bound in the request lifecycle.

How to reproduce:

1. Enable telemetry in config.js and have it print to the console on a publish interval of 1 second
2. Start your server and browse the application
3. Look at the console, you'll find entries for GET`undefined.count and GET`undefined.time but nothing for the actual paths