Jira (PUP-6275) Compiler PROFILE output should be logged at INFO level
Title: Message Title John Duarte updated an issue Puppet / PUP-6275 Compiler PROFILE output should be logged at INFO level Change By: John Duarte QA Risk Assessment: Low Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6275) Compiler PROFILE output should be logged at INFO level
Title: Message Title John Duarte updated an issue Puppet / PUP-6275 Compiler PROFILE output should be logged at INFO level Change By: John Duarte QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6275) Compiler PROFILE output should be logged at INFO level
Title: Message Title John Duarte assigned an issue to qa Puppet / PUP-6275 Compiler PROFILE output should be logged at INFO level Change By: John Duarte Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6275) Compiler PROFILE output should be logged at INFO level
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-6275
Compiler PROFILE output should be logged at INFO level
Change By:
Henrik Lindberg
Release Notes Summary:
Compiler profiling is now output at log level {{info}} which removes the need to bump the log level to {{debug}}. This makes it convenient to get only the profiling information without having to restart the puppet server .
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6275) Compiler PROFILE output should be logged at INFO level
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-6275
Compiler PROFILE output should be logged at INFO level
Change By:
Henrik Lindberg
Acceptance Criteria:
That profiling information is generated at loglevel {{info}} to avoid having to dig out the profiling information from massive amounts of debug output.
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6275) Compiler PROFILE output should be logged at INFO level
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-6275
Compiler PROFILE output should be logged at INFO level
Change By:
Henrik Lindberg
Release Notes Summary:
Compiler profiling is now output at log level {{info}} which removes the need to bump the log level to {{debug}}. This makes it convenient to get only the profiling information.
Sprint:
Language Triage 2016-09-07
Release Notes:
New Feature
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6275) Compiler PROFILE output should be logged at INFO level
Title: Message Title Charlie Sharpsteen commented on PUP-6275 Re: Compiler PROFILE output should be logged at INFO level Looks like bumping that to :info has the desired effect. Submitted a PR. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6275) Compiler PROFILE output should be logged at INFO level
Title: Message Title Henrik Lindberg commented on PUP-6275 Re: Compiler PROFILE output should be logged at INFO level Thanks Chris Price and Charlie Sharpsteen Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6275) Compiler PROFILE output should be logged at INFO level
Title: Message Title Charlie Sharpsteen assigned an issue to Charlie Sharpsteen Puppet / PUP-6275 Compiler PROFILE output should be logged at INFO level Change By: Charlie Sharpsteen Assignee: Charlie Sharpsteen Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6275) Compiler PROFILE output should be logged at INFO level
Title: Message Title Charlie Sharpsteen commented on PUP-6275 Re: Compiler PROFILE output should be logged at INFO level Sure, I'll take a look at it. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6275) Compiler PROFILE output should be logged at INFO level
Title: Message Title Chris Price assigned an issue to Unassigned Puppet / PUP-6275 Compiler PROFILE output should be logged at INFO level Change By: Chris Price Assignee: Chris Price Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6275) Compiler PROFILE output should be logged at INFO level
Title: Message Title Chris Price commented on PUP-6275 Re: Compiler PROFILE output should be logged at INFO level For the profiler info that Charlie Sharpsteen is talking about, I think it ends up at debug level due to this line: https://github.com/puppetlabs/puppet/blob/master/lib/puppet/network/http/handler.rb#L170 I have no objection to changing that; Charlie Sharpsteen perhaps you can confirm that changing that line will indeed give us the behavior that you are after? Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6275) Compiler PROFILE output should be logged at INFO level
Title: Message Title Henrik Lindberg assigned an issue to Chris Price Puppet / PUP-6275 Compiler PROFILE output should be logged at INFO level Change By: Henrik Lindberg Assignee: Chris Price Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6275) Compiler PROFILE output should be logged at INFO level
Title: Message Title Henrik Lindberg commented on PUP-6275 Re: Compiler PROFILE output should be logged at INFO level Ping Chris Price I think the logic for this is on the Puppet Server side. Is that correct? Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6275) Compiler PROFILE output should be logged at INFO level
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6275 Compiler PROFILE output should be logged at INFO level Change By: Henrik Lindberg Story Points: 2 Fix Version/s: PUP 4.7.0 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6275) Compiler PROFILE output should be logged at INFO level
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6275 Compiler PROFILE output should be logged at INFO level Change By: Henrik Lindberg Sprint: Language Triage Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6275) Compiler PROFILE output should be logged at INFO level
Title: Message Title Charlie Sharpsteen created an issue Puppet / PUP-6275 Compiler PROFILE output should be logged at INFO level Issue Type: Improvement Assignee: Unassigned Components: Language Created: 2016/05/06 3:33 PM Priority: Normal Reporter: Charlie Sharpsteen The profile setting causes the compiler to output timing information during catalog compilation. This output can be enabled for all compilations by setting profile="" in the master's settings or on an agent-by-agent basis using the profile setting or profile flag. However, the profiling results are logged at DEBUG level by the master, which means that the master's log level has to be adjusted prior to profiling, and then reset to INFO after profiling both changes require a restart or reload of the master process. Given that a user already has to pass an agent flag or add a setting to trigger profile output, this data should be logged at the default level, which is INFO for Puppet Server. This change would allow agents to be profiled on demand without the need to restart or reload any Puppet Server processes. Current Behavior Profile output is logged at DEBUG level, so the log level must be temporarily increased which requires two or more Puppet Server restarts or reloads and, often manual, edits to server configuration. Desired Behavior When puppet agent -t --profile is run on an agent, PROFILE output shows up in the Puppet Server logs without any need to edit server
