404s in CKAN are reported to New Relic as individual events

[adborden]

New Relic notified us that there were a large number of unique transactions being produced on inventory. This was caused by a third-party pen test or scan. However, the 404 controller could be improved so that these routes aren't reported to NR as unique events.

From New Relic support:

It looks like those requests resulted in redirects - is the app able to call https://docs.newrelic.com/docs/agents/python-agent/python-agent-api/set_transaction_name when that happens? That way you could group those accordingly.

How to reproduce

1. Open your browser to https://inventory.data.gov/.well-known to produce a 404.
2. In New Relic, open the transactions table

Expected behavior

404 routes are grouped together under the 404 controller.

Actual behavior

Many routes are listed as unique transactions, e.g. /.well-known