NotFound exceptions should be ignored by the error monitor
Bug #1018909 reported by
Paul Everitt
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
KARL3 |
Fix Released
|
Medium
|
Chris Rossi |
Bug Description
NotFound exceptions percolate up into the error monitor and raise an alarm. They shouldn't.
This was actually caused by some misbehaving Chatter code, which was causing all errors to be turned into General Errors. You'll find that on production, currently, going to any URL that should be a NotFound will generate an General Error and trip the alarm. This is now fixed on the branch, fix_notfound.
Additionally, it became apparent that it might be useful to track not found errors as long as they don't trip the alarm, so I also added some code to log NotFound errors to the redislog using the NOTFOUND category, which does not trip the alarm.