-
Notifications
You must be signed in to change notification settings - Fork 278
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
Allow option to disable resource.name 404 rewriting #458
Comments
@rymndhng Is this instrumentation for a server? If so how would you know which resource to associate the 404 with? For example, if you had two endpoints |
@realark I think I see where you're coming from. In the case where there is no tag The current implementation always sets the |
@rymndhng can you explain the circumstance where the 404 being returned by the application is useful to not group together? |
The cirumstance where the 404s are not useful to be grouped together is because applications may implement generic routes with a different permission scheme. i.e. if I am seeing a huge number of 404s on the url pattern |
Resolved with #1152 |
The datadog documention recommends to reduce the cardinality of the
resource.name
, and most of the instrumentation is cognizant of this. What's the scenario where the Status404Decorator is useful?The decorator here rewrites 404 responses with a custom
resource.name
. This was very confusing for me because I was expecting to look at the ratio of 404s to non-404s for my resource.Can we add an option to turn this decorator off? I would like to have the ability to see my 404 responses with their original
resource.name
.The text was updated successfully, but these errors were encountered: