The Puppet Labs Issue Tracker has Moved: https://tickets.puppetlabs.com
https://tickets.puppetlabs.com. See the following page for information on filing tickets with JIRA:
Add support to control verbosity of masterhttp.log
|Affected Puppet version:||0.25.5||Branch:|
Ticket tracking is now hosted in JIRA: https://tickets.puppetlabs.com
I am trying to reduce the verbosity of masterhttp.log by adding the option ‘rails_loglevel = err’ to the main section of puppet.conf (I tried also puppetd and puppetmasterd for that matter). However when I run:
puppet --configprint rails_loglevel
It keeps saying ‘info’ regardless of that I pass in the config file. I looked at puppet init scripts thinking that it would get overwritten, but that does not seem to be the case. I can’t seem to find a way to change the log level, as the master keeps printing pretty much every thing it can.
Is there any way I can tune the log level down? Is this a bug or a misconfiguration?
#1 Updated by James Turnbull about 5 years ago
- Category set to logging
- Status changed from Unreviewed to Needs More Information
The rails_loglevel is unrelated to masterhttp.log. The Rails log level is used for the Rails ORM which is mostly used for Stored Configurations.
I don’t think the current masterhttplog file’s verbosity can be configured but I will check.
#3 Updated by James Turnbull about 5 years ago
- Tracker changed from Bug to Feature
- Subject changed from Cannot control verbosity of masterhttp.log to Add support to control verbosity of masterhttp.log
- Status changed from Needs More Information to Needs Decision
- Assignee set to Nigel Kersten
Okay I checked there isn’t a way to change the verbosity of the logging.
It would be simple to add:
- Add an option in lib/puppet/defaults.rb for masterhttploglevel or something better named.
- Edit the httplog method in lib/puppet/network/http_server/webrick.rb.
- Then add a test in spec/unit/network/http/webrick_spec.rb