-
Notifications
You must be signed in to change notification settings - Fork 229
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
(#780) puppetserver: don't purge metrics.conf / Use dedicated parameter for jruby profiler #781
(#780) puppetserver: don't purge metrics.conf / Use dedicated parameter for jruby profiler #781
Conversation
that's my (currently untested) approach to fix #780 . Let me know what you think / if you like two PRs for this. |
4983f58
to
fe45a60
Compare
Other than the failing unit tests, I think this looks good. I already started to change the odd |
This introduces a new parameter to disable the profiling indepently from the metrics. Previously this was enabled by default. However Puppet Inc. disables it in their standard configuration and the profiler causes a significate memory and CPU overhead so I guess we should stick with the upstream default.
This parameter only enables/disables the *http-client* metrics within puppetserver. It's disabled by default in the Puppet Inc. config file.
6f37175
to
44a0400
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me, let's see if the test agree.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Test failures look unrelated, merging.
This introduces a new parameter to disable the profiling indepently from
the metrics. Previously this was enabled by default. However Puppet Inc.
disables it in their standard configuration and the profiler causes a
significate memory and CPU overhead so I guess we should stick with the
upstream default.