Jira (PUP-2997) Logdest cannot be set in the puppet.conf

[Mike Andrewjeski (JIRA)]

Mike Andrewjeski commented on PUP-2997

Re: Logdest cannot be set in the puppet.conf I know Cecilia Cottle has raised this a an issue for several puppetlabs customers, and I just want to add that we (BusinessWire) would also like to see this resolved. While we can modify the init script to handle, we'd rather not. Add Comment

This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)

[Bartlomiej Sternal (JIRA)]

Bartlomiej Sternal commented on PUP-2997

Re: Logdest cannot be set in the puppet.conf

I second the request. This is an annoyance for us at Dynatrace, on windows machines in particular. Puppet spams the event log making it hard to find anything worthwhile.

Add Comment

This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)

[Darrin Chambers (JIRA)]

Darrin Chambers commented on PUP-2997

Re: Logdest cannot be set in the puppet.conf

We just switched to Splunk for log tracking and this is an issue for us.

Add Comment

This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)

[Charlie Sharpsteen (JIRA)]

Charlie Sharpsteen assigned an issue to Unassigned

Puppet / PUP-2997

Logdest cannot be set in the puppet.conf

Change By: Charlie Sharpsteen Assignee: Charlie Sharpsteen Scrum Team: Client Platform

Add Comment

[Charlie Sharpsteen (JIRA)]

Charlie Sharpsteen updated an issue

Puppet / PUP-2997 Logdest cannot be set in the puppet.conf

Change By: Charlie Sharpsteen Affects Version/s: PUP 3.8.7 Affects Version/s: PUP 4.8.1 CS Priority: Needs Priority Team: Agent & Platform

Add Comment

This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)

[Eric Sorenson (JIRA)]

Eric Sorenson updated an issue

Puppet / PUP-2997 Logdest cannot be set in the puppet.conf

Change By: Eric Sorenson Team: Agent & Platform Analytics

Add Comment

[Eric Sorenson (JIRA)]

Eric Sorenson updated an issue

Puppet / PUP-2997 Logdest cannot be set in the puppet.conf

Change By: Eric Sorenson Sprint: AP Grooming 2017-02-01

Add Comment

[Eric Sorenson (JIRA)]

Eric Sorenson updated an issue

Puppet / PUP-2997 Logdest cannot be set in the puppet.conf

Change By: Eric Sorenson Team: Analytics Agent & Platform

Add Comment

[Eric Sorenson (JIRA)]

Eric Sorenson commented on PUP-2997

Re: Logdest cannot be set in the puppet.conf Closing this as won't fix. Sorry, but there are viable workarounds (just specify it on the command line) and the interaction between settings and logging create lots of chicken-and-egg problems (which is why this situation arose in the first place).

Add Comment

[Geoff Nichols (JIRA)]

Geoff Nichols updated an issue

Puppet / PUP-2997

Logdest cannot be set in the puppet.conf

Change By: Geoff Nichols Sprint: Agent Grooming

Add Comment

[Ryan Coleman (JIRA)]

Ryan Coleman commented on PUP-2997

Re: Logdest cannot be set in the puppet.conf Eric Sorenson, are any of the viable workarounds documented? If not, could you point me at a ticket to track adding those to the appropriate part of the docs?

Add Comment

[Eric Sorenson (JIRA)]

Eric Sorenson commented on PUP-2997

Re: Logdest cannot be set in the puppet.conf

Ryan Coleman it's in the description - you can use a command line argument.

Add Comment

[Charlie Sharpsteen (JIRA)]

Charlie Sharpsteen commented on PUP-2997

Re: Logdest cannot be set in the puppet.conf

There's one use case that we don't have a great workaround for: ensuring puppet logs go to the same source regardless of how the command is invoked. If you want Puppet daemon logs to go to a specific file, that's easy enough to configure by adding - logdest to /etc/sysconfig or a similar location. However, if you also want all invocations of puppet agent -t to log to the same file, then you're stuck in a bit of a bind. You could tell everyone to make sure they pass -logdest when running puppet, but that's going to have a high failure rate. You could write a wrapper for the Puppet command that ensures the flag is added, but that's a bit of site-specific work and carries the risk of breaking the system in ways that are hard to debug. Being able to set the log destinations in the central Puppet configuration file would be a really nice solution to this problem.

Add Comment

[Robert J (JIRA)]

Robert J commented on PUP-2997

Re: Logdest cannot be set in the puppet.conf

Amazing that people are requesting this and Puppetlabs has deemed it not worth fixing. There are some pretty good reasons WHY using the CLI is not a good workaround which have already been stated.

Add Comment

This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)

[Eric Sorenson (JIRA)]

Eric Sorenson updated an issue

Puppet / PUP-2997

Logdest cannot be set in the puppet.conf

Change By: Eric Sorenson Sprint: Platform Core Hopper

Add Comment

[Eric Sorenson (JIRA)]

Eric Sorenson updated an issue

Puppet / PUP-2997 Logdest cannot be set in the puppet.conf

Change By: Eric Sorenson Team: Agent Coremunity

Add Comment

[Charlie Sharpsteen (JIRA)]

Charlie Sharpsteen updated an issue

Puppet / PUP-2997 Logdest cannot be set in the puppet.conf

Change By: Charlie Sharpsteen Affects Version/s: PUP 4.10.10 Affects Version/s: PUP 5.5.0

Add Comment

[Owen Rodabaugh (JIRA)]

Owen Rodabaugh updated an issue

Puppet / PUP-2997 Logdest cannot be set in the puppet.conf

Change By: Owen Rodabaugh CS Priority: Needs Priority Normal CS Impact: Users sometimes want to send their logs to a different location and have this work for ALL invocations of puppet(daemon or CLI). Example cases mentioned in this ticket are to send everything to splunk, or to make the puppet logs available to less privileged users. The wrapper script that was added in Puppet 5 could be modified to source a logdest from some other file such as puppet.conf or if that isn't workable something like environment settings such as sysconfig CS Severity: 3 - Serious CS Business Value: 4 - $$$$$ CS Frequency: 2 - 5-25% of Customers

Add Comment

[R.I.Pienaar (JIRA)]

R.I.Pienaar commented on PUP-2997

Re: Logdest cannot be set in the puppet.conf The chicken and egg here is that, where do you log when you can't find the config file to tell you where to log? or cant read it? etc Logging it to a default fallback STDERR would be wrong - because then if someone monitors splunk they dont know about it. Specifying it on the CLI only ensures that in all cases the right thing can be done (or at least tried).

Add Comment

[Robert J (JIRA)]

Robert J commented on PUP-2997

Re: Logdest cannot be set in the puppet.conf

Then you default log it to the system syslog like it does now...

Add Comment

[R.I.Pienaar (JIRA)]

R.I.Pienaar commented on PUP-2997

Re: Logdest cannot be set in the puppet.conf

But it doesn't in so many cases puppet apply, puppet agent --test, etcetc. There's no right thing that handles all cases other than let people tell it what to do always.

Add Comment

[R.I.Pienaar (JIRA)]

R.I.Pienaar commented on PUP-2997

Re: Logdest cannot be set in the puppet.conf

And if someone goes to the trouble of setting up lets say splunk logging or whatever, and make Puppet log there, it's a safe assumption thats where they want to look for problems with puppet. Fall back default that is not where they look for critical errors is grossly irresponsible. I don't care either way, I am just pointing out why things are as they are for some context

Add Comment

[Craig Gomes (JIRA)]

Craig Gomes updated an issue

Puppet / PUP-2997

Logdest cannot be set in the puppet.conf

Change By: Craig Gomes Fix Version/s: PUP 5.5.z

Add Comment

[Jacob Helwig (JIRA)]

Jacob Helwig assigned an issue to Jacob Helwig

Puppet / PUP-2997 Logdest cannot be set in the puppet.conf

Change By: Jacob Helwig Assignee: Jacob Helwig

Add Comment

[Jacob Helwig (JIRA)]

Jacob Helwig updated an issue

Puppet / PUP-2997 Logdest cannot be set in the puppet.conf

Change By: Jacob Helwig Sprint: Platform Core Hopper KANBAN

Add Comment

[Jacob Helwig (JIRA)]

Jacob Helwig updated an issue

Puppet / PUP-2997 Logdest cannot be set in the puppet.conf

Change By: Jacob Helwig Release Notes Summary: The `--logdest` argument can now also be set in the puppet.conf file as the `logdest` setting. Release Notes: New Feature

Add Comment

[Josh Cooper (JIRA)]

Josh Cooper updated an issue

Puppet / PUP-2997 Logdest cannot be set in the puppet.conf

Change By: Josh Cooper Fix Version/s: PUP 5.5.z Fix Version/s: PUP 5.5.7

Add Comment

[Josh Cooper (JIRA)]

Josh Cooper updated an issue

Puppet / PUP-2997 Logdest cannot be set in the puppet.conf

Change By: Josh Cooper Fix Version/s: PUP 6.0.3

Add Comment

[Jacob Helwig (JIRA)]

Jacob Helwig commented on PUP-2997

Re: Logdest cannot be set in the puppet.conf Merged to 5.5.x in 72c9376bf1. Merged to 6.0.x in d2c97237f5.

Add Comment

[Austin Boyd (JIRA)]

Austin Boyd updated an issue

Puppet / PUP-2997

Logdest cannot be set in the puppet.conf

Change By: Austin Boyd Zendesk Ticket IDs: 34390 Zendesk Ticket Count: 1

Add Comment