You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a "default route" in my application which proxies requests to another service I think this is a somewhat common pattern -a default route in Express. Something like:
When I do this, it is causing some noisey routes in monitoring because each unique path which triggers this route is reported and aggregated separely. For example a request to /does-not-exist.txt is reported as route does-not-exist.txt*.
I'm thinking to resolve this by special casing the '*' route and reporting this in Prometheus under the simple consistent value * (no additional path information).
An alternative solution (if this is not a common case encountered for others), would be to provide a public interface which allows me to define my own mapping from route to string).
The text was updated successfully, but these errors were encountered:
Thanks for reporting the issue.
I believe that using wildcard is a valid use-case and should be supported out-the-box, just as we do with variable path params.
As I currently don't have the capacity for handling it myself, I'd gladly accept PRs.
I have a "default route" in my application which proxies requests to another service I think this is a somewhat common pattern -a default route in Express. Something like:
When I do this, it is causing some noisey routes in monitoring because each unique path which triggers this route is reported and aggregated separely. For example a request to
/does-not-exist.txt
is reported as routedoes-not-exist.txt*
.I'm thinking to resolve this by special casing the
'*'
route and reporting this in Prometheus under the simple consistent value*
(no additional path information).An alternative solution (if this is not a common case encountered for others), would be to provide a public interface which allows me to define my own mapping from route to string).
The text was updated successfully, but these errors were encountered: