Allow option to disable resource.name 404 rewriting
See original GitHub issueThe 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
.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:3
- Comments:5 (3 by maintainers)
Top Results From Across the Web
IIS URL rewrite - reverse proxy - responding with 404 error
For me, this worked on IIS: Go to IIS root node >> ARR. enter image description here. Click "Server Proxy Settings" option.
Read more >How to Fix WordPress 404 Not Found Error [8 Easy Solutions]
This blog shares the easy fixes to bypass the 404 error on your WordPress site. ... Navigate to your database name, and select...
Read more >URL Rewriting Middleware in ASP.NET Core - Microsoft Learn
This article introduces URL rewriting with instructions on how to use URL Rewriting Middleware in ASP.NET Core apps. URL rewriting is the ...
Read more >How To Rewrite URLs with mod_rewrite for Apache on ...
Step 1 — Enabling mod_rewrite · Step 2 — Setting Up .htaccess · Step 3 — Configuring URL Rewrites.
Read more >How to Set a Custom 404 Page With .htaccess
htaccess file. This will allow you to set the error message that visitors to your site receive when they request a page that...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
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
/foo/:id/bar/:id
, I want to see the spans with 404s grouped under the same resource name/foo/:id/bar/:id
instead of a catch-all404
.Resolved with #1152