-
Notifications
You must be signed in to change notification settings - Fork 68
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Airbrake performance changes are filling logs with deprecation messages #532
Comments
And it's costing me money, as my Papertrail log volume has gone through the roof. |
Mine as well. We keep running out, and then we have no logging for our app. |
Sorry about this. I would recommend locking |
Resolves airbrake/airbrake-ruby#532 (Airbrake performance changes are filling logs with deprecation messages) This was inroduced by airbrake/airbrake-ruby#526 We can now pass `event.duration`, so there's no need to calculate it again. This is more accurate as well since we pass monotonic time instead of realtime.
Resolves airbrake/airbrake-ruby#532 (Airbrake performance changes are filling logs with deprecation messages) This was inroduced by airbrake/airbrake-ruby#526 We can now pass `event.duration`, so there's no need to calculate it again. This is more accurate as well since we pass monotonic time instead of realtime.
I just released |
Required to remove deprecation warnings that spam our logs. See airbrake/airbrake-ruby#532.
In our logs since upgrading to 4.11.1 our logs are FULL (literally 2 lines per each controller load) of this:
We do a lot of work to make sure our logs are clean and relevant. This deprecation warning is literally 66% of our logs at this point (as we use Lograge and each controller's log is 1 line). And, it's not 1 time, it's literally on every request.
The text was updated successfully, but these errors were encountered: