The Puppet Labs Issue Tracker has Moved: https://tickets.puppetlabs.com

This issue tracker is now in read-only archive mode and automatic ticket export has been disabled. Redmine users will need to create a new JIRA account to file tickets using https://tickets.puppetlabs.com. See the following page for information on filing tickets with JIRA:

Feature #20173

Logdest cannot be set in the puppet.conf

Added by Celia Cottle over 2 years ago. Updated 12 months ago.

Status:InvestigatingStart date:
Priority:NormalDue date:
Assignee:Charlie Sharpsteen% Done:

0%

Category:logging
Target version:-
Affected Puppet version: Branch:
Keywords:customer

We've Moved!

Ticket tracking is now hosted in JIRA: https://tickets.puppetlabs.com

This ticket is now tracked at: https://tickets.puppetlabs.com/browse/PUP-2997


Description

This is potentially a duplicate issue of a few things floating around out there, but most focus on masterlog, so I’m opening this up separately. Currently you can use —logdest /var/log/somelogfile, but you cannot set it in the puppet.conf. This seems like an oversight, especially since there seems to be a good number of people who wish to keep all puppet logs out of /var/log/messages. There are ways around this (etc/init.d/pe-puppet), but they are purely workarounds. It looks like some of the reason for this is the old masterlog option, which it seems is no longer in use, used to be the preferred way of setting in the puppet.conf.

Potentially related tickets: https://projects.puppetlabs.com/issues/5952 https://projects.puppetlabs.com/issues/4550 https://projects.puppetlabs.com/issues/12361


Related issues

Related to Puppet - Bug #5952: Fix logdir, logdest and other disaster options Rejected 01/20/2011
Related to Puppet - Bug #12361: "masterlog" option does not appear to be used Code Insufficient 02/01/2012
Related to Puppet - Feature #4761: Allow verbose and debug options to be specified in config... Accepted 09/14/2010

History

#1 Updated by Celia Cottle over 2 years ago

  • Keywords set to customer

#3 Updated by Charlie Sharpsteen about 2 years ago

  • Assignee set to Charlie Sharpsteen

#4 Updated by Charlie Sharpsteen about 2 years ago

  • Category set to logging
  • Status changed from Unreviewed to Investigating

I’ll see what can be done about this. Looks like there is also some documentation that needs to be fixed (ref #12361)

#5 Updated by Anonymous about 2 years ago

  • Tracker changed from Bug to Feature

The issue here is that logdest is not a setting, which would make it global to all subcommands and available to be set in puppet.conf. This isn’t really a bug, but a feature request to make logdest behave in a better manner. Not a big deal, but a slight clarification.

#6 Updated by Eddie Satterly over 1 year ago

This is required for core functionality to build the a Splunk app for Puppet and to be able to track all changes and show the current health of the Puppet system in Splunk. This is a request from several Splunk customers.

#7 Updated by eric sorenson over 1 year ago

Eddie—can you clarify why the Splunk integrations require a puppet.conf setting rather than a command line option?

#8 Updated by Eddie Satterly over 1 year ago

A Splunk app has no way of checking if the service is logging where it is supposed to be and there are just no entries, or if the service has started with a certain cmd line switch easily. In the case of a config file that is out of the box for us as we use .conf files as well so we could check state and verify if in failure condition or just no activity. Otherwise we would have to do custom command for ps-ef with grep for service invocation and parse for cmd line switch and that is ugly and prone to issues, especially with version changes.

#9 Updated by Charlie Sharpsteen 12 months ago

Redmine Issue #20173 has been migrated to JIRA:

https://tickets.puppetlabs.com/browse/PUP-2997

Also available in: Atom PDF