Skip to content
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

config: enable performance_stats by default #485

Merged
merged 1 commit into from Jun 25, 2019
Merged

Conversation

kyrylo
Copy link
Contributor

@kyrylo kyrylo commented Jun 24, 2019

No description provided.

@kyrylo kyrylo merged commit 9426019 into master Jun 25, 2019
@kyrylo kyrylo deleted the performance-stats-true branch June 25, 2019 11:49
kyrylo added a commit to airbrake/airbrake that referenced this pull request Jul 1, 2019
With [`performance_stats = true`][1] Airbrake generates a lot of logs now. This
causes some inconvenience in the development environment because Rails uses
`debug` severity for its logger.

We don't have a lot of places where we log but we do log frequently (on every
request we log performance data for that request). Simply removing that debug
output would solve the issue but we need it so we can debug the library.

The best decision would be using a separate file, where we can be noisy without
annoying our users. If we ever need that debug output, we can ask the users to
check `airbrake.log`.

[1]: airbrake/airbrake-ruby#485
kyrylo added a commit to airbrake/airbrake that referenced this pull request Jul 1, 2019
With [`performance_stats = true`][1] Airbrake generates a lot of logs now. This
causes some inconvenience in the development environment because Rails uses
`debug` severity for its logger.

We don't have a lot of places where we log but we do log frequently (on every
request we log performance data for that request). Simply removing that debug
output would solve the issue but we need it so we can debug the library.

The best decision would be using a separate file, where we can be noisy without
annoying our users. If we ever need that debug output, we can ask the users to
check `airbrake.log`.

[1]: airbrake/airbrake-ruby#485
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant