From 1b4efd216485ae21798d1a7330fc91300d699512 Mon Sep 17 00:00:00 2001 From: Maikel Linke Date: Thu, 14 Nov 2024 15:30:41 +1100 Subject: [PATCH] Revert "Notify bugsnag on 404 errors" This reverts commit 2eec3d625a8f1c0b06560cbdc67b0e1646d03b3c. We started tracking 404 errors out of interest without an actual problem to solve. Now we face rate-limiting in our Bugsnag account. And we didn't use these 404 reports in the two years this code was active. We don't even act on all 500 errors. So while our resources are so constrained, let's keep our focus on the severe errors and user reports and ignore the rest. 404 errors are mostly generated by vulnerability scanners. --- app/controllers/errors_controller.rb | 5 ----- 1 file changed, 5 deletions(-) diff --git a/app/controllers/errors_controller.rb b/app/controllers/errors_controller.rb index 262325f029..f071ae64f5 100644 --- a/app/controllers/errors_controller.rb +++ b/app/controllers/errors_controller.rb @@ -4,11 +4,6 @@ class ErrorsController < ApplicationController layout "errors" def not_found - Bugsnag.notify("404") do |event| - event.severity = "info" - - event.add_metadata(:request, :env, request.env) - end render status: :not_found, formats: :html end