-
Notifications
You must be signed in to change notification settings - Fork 8.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Retrieve handler RouteInfo #649
Comments
#584 was originally opened to support this. It appears that the original issue creator would like something similar to what I would like, and I'd be willing to take a crack at a PR, but figured I'd open an issue first to see if thoughts on whether it would be appreciated since the original issue was closed. It would be great to see the selected Route available for introspection on the Context object. Right now, when one of our global middleware throws an exception, we can't track what the end path was going to be by handler. |
I would like to see this as well. It's very good for instrumentation where you'd like to aggregate statistics by route (e.g. |
We would also need this. I did an ugly workarround in a middleware the mean time:
I guess its also affecting performance since every call is looping over all routes. But until this issue is resolved i think its the only way. |
When a request hits Gin, it would be great for instrumentation to have access to the original route string that was passed to register the handler that has been selected to handle the request.
The text was updated successfully, but these errors were encountered: