Console logs are being polluted after latest version bump

[mikewcaldwell]

This started happening after the latest version.

I see that you can add HONEYBADGER_INSIGHTS_ENABLED=false before launching the console, is there a more straightforward way so that we don't have to do this every console startup? Our team is not signed up to use insights, so even receiving these errors seems excessive.

3.2.2 :006 > 2024-07-05 13:28:36.987204 W [3218533:245600 logging.rb:98] Rails -- ** [Honeybadger] Event send failed: project is sending too many events. code=429 throttle=1 interval=0.05 level=2 pid=3218533 -- honeybadger
2024-07-05 13:28:45.746213 I [3218533:245620 redis_connection.rb:15] Sidekiq -- Sidekiq 7.3.0 connecting to Redis with options {:size=>10, :pool_name=>"internal", :url=>""}
2024-07-05 13:29:36.981770 W [3218533:245600 logging.rb:98] Rails -- ** [Honeybadger] Event send failed: project is sending too many events. code=429 throttle=2 interval=0.103 level=2 pid=3218533 -- honeybadger
2024-07-05 13:30:36.970057 W [3218533:245600 logging.rb:98] Rails -- ** [Honeybadger] Event send failed: project is sending too many events. code=429 throttle=3 interval=0.158 level=2 pid=3218533 -- honeybadger
2024-07-05 13:31:36.971423 W [3218533:245600 logging.rb:98] Rails -- ** [Honeybadger] Event send failed: project is sending too many events. code=429 throttle=4 interval=0.216 level=2 pid=3218533 -- honeybadger
2024-07-05 13:32:36.970057 W [3218533:245600 logging.rb:98] Rails -- ** [Honeybadger] Event send failed: project is sending too many events. code=429 throttle=5 interval=0.276 level=2 pid=3218533 -- honeybadger
2024-07-05 13:33:37.023914 W [3218533:245600 logging.rb:98] Rails -- ** [Honeybadger] Event send failed: project is sending too many events. code=429 throttle=6 interval=0.34 level=2 pid=3218533 -- honeybadger

[stympy]

Thanks for the report! The fix for this will be in version 5.13.3, which should be available on Monday.