-
Notifications
You must be signed in to change notification settings - Fork 35
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
[Feature Request] Group unhandled paths instead of filter #82
Comments
@Filipoliko that sounds useful. Do you envision a new metric or a special value of |
@stephenhillier I've been thinking about a special value of I was thinking
I checked how other projects are handling this.
But it is difficult to find examples. Some projects are offering users to implement some sort of custom url path transformers so they can handle it any way they want. |
I think either value sounds reasonable 👍 Don't feel like you need to make it configurable right away (your choice), that could be added later if somebody needs it. |
Hi,
just ran into this #79 issue and im glad to see the new defaults. It definitely makes sense to me.
Im just a bit worried about
filter_unhandled_paths=True
throwing away information about some 404 requests. I think we are missing out on some potentially key information about what kinds of requests are being sent to the server. Instead of filtering, wouldn't it make sense to group these requests under someothers
/unhandled
value?If this sounds interesting, there could be a new flag
group_unhandled_paths
created. If set toTrue
, it could group all unhandled paths into some common value for these unhandled requests. The other flag namefilter_unhandled_paths
does not make much sense to implement this kind of logic, so it makes more sense to me to create a new one.If there is agreement, I would be happy to create a PR.
The text was updated successfully, but these errors were encountered: