Suppress HttpException.404 for bad URLs Requests for non-existent templates/pages (404s) result in an uncaught HttpException.404 being thrown, though the correct 404 template is displayed. Is there some way to suppress or handle this exception? It's flooding my error reporting tool. For reference, here's the stack trace from the log:

2016/12/07 17:29:07 [error] [exception.Craft\HttpException.404] exception 'Craft\HttpException' in /project/craft/app/controllers/TemplatesController.php:59
Stack trace:
#0 [internal function]: Craft\TemplatesController-&gt;actionRender('page-no-existy', Array)
#1 /project/craft/app/framework/web/actions/CAction.php(109): ReflectionMethod-&gt;invokeArgs(Object(Craft\TemplatesController), Array)
#2 /project/craft/app/framework/web/actions/CInlineAction.php(47): CAction-&gt;runWithParamsInternal(Object(Craft\TemplatesController), Object(ReflectionMethod), Array)
#3 /project/craft/app/framework/web/CController.php(308): CInlineAction-&gt;runWithParams(Array)
#4 /project/craft/app/framework/web/CController.php(286): CController-&gt;runAction(Object(CInlineAction))
#5 /project/craft/app/framework/web/CController.php(265): CController-&gt;runActionWithFilters(Object(CInlineAction), Array)
#6 /project/craft/app/framework/web/CWebApplication.php(282): CController-&gt;run('render')
#7 /project/craft/app/framework/web/CWebApplication.php(141): CWebApplication-&gt;runController('templates/rende...')
#8 /project/craft/app/etc/web/WebApp.php(290): CWebApplication-&gt;processRequest()
#9 /project/craft/app/framework/base/CApplication.php(185): Craft\WebApp-&gt;processRequest()
#10 /project/craft/app/index.php(62): CApplication-&gt;run()
#11 /project/src/static/index.php(21): require_once('/project...')
#12 {main}
REQUEST_URI=/page-no-existy
The good news in the upcoming Craft 3 this isn't an issue.  404's get logged to their own separate log files and won't clutter up the main Craft log files specifically for this reason.

In Craft 2, I think you'd have to do something like write a plugin that listens for Yii's onException event, makes sure it's a 404 status code, then go through Yii's CLogger to get the full list of log entries and remove the last one.