Jira (BOLT-453) Use more readable log format for the console.
Title: Message Title Kate Lopresti updated an issue Puppet Task Runner / BOLT-453 Use more readable log format for the console. Change By: Kate Lopresti Labels: docs-reviewed feature Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 (BOLT-453) Use more readable log format for the console.
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-453 Use more readable log format for the console. Change By: Alex Dreyer Release Notes Summary: This changes the output format on stderr removing the log formatting that made it hard to read. Release Notes: New Feature Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 (BOLT-453) Use more readable log format for the console.
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-453 Use more readable log format for the console. Change By: Alex Dreyer Fix Version/s: BOLT Next Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 (BOLT-453) Use more readable log format for the console.
Title: Message Title Michael Smith assigned an issue to Unassigned Puppet Task Runner / BOLT-453 Use more readable log format for the console. Change By: Michael Smith Assignee: Michael Smith Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 (BOLT-453) Use more readable log format for the console.
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet Task Runner / BOLT-453 Use more readable log format for the console. Change By: Michael Smith Assignee: Nick Lewis Michael Smith Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 (BOLT-453) Use more readable log format for the console.
Title: Message Title Nick Lewis assigned an issue to Nick Lewis Puppet Task Runner / BOLT-453 Use more readable log format for the console. Change By: Nick Lewis Assignee: Nick Lewis Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 (BOLT-453) Use more readable log format for the console.
Title: Message Title
Michael Smith updated an issue
Puppet Task Runner / BOLT-453
Use more readable log format for the console.
Change By:
Michael Smith
The log format makes sense for logging to file but is hard to read on the CLI. Now that we have separate loggers for file and console logging we should use a more succinct format for the console.What is the desired format.Only print the message. Use color to differentiate between error(red), warn(yellow), notice(green) and everything else uncolored.current:{noformat}$ bolt plan run my_app::deploy version=1.0.2 app_servers=app db_server=db lb_server=lb --inventoryfile ./inventory.yaml --modulepath=./modules2018-04-05T11:01:18.711945 NOTICE Bolt::Executor: Starting: Check load before starting deploy on ["0.0.0.0:32771"]2018-04-05T11:01:18.969123 NOTICE Bolt::Executor: Finished: Check load before starting deploy on 1 node with 0 failures2018-04-05T11:01:18.973994 NOTICE Bolt::Executor: Starting: Install 1.0.2 of the application on ["0.0.0.0:32768", "0.0.0.0:32769", "0.0.0.0:32770"]2018-04-05T11:01:19.237311 NOTICE Bolt::Executor: Finished: Install 1.0.2 of the application on 3 nodes with 0 failures2018-04-05T11:01:19.262561 NOTICE Bolt::Executor: Starting: task my_app::lb on ["0.0.0.0:32771"]2018-04-05T11:01:19.413007 NOTICE Bolt::Executor: Finished: task my_app::lb on 1 node with 0 failuresNotice: Scope(/my_app/plans/deploy.pp, 47): Backend 0.0.0.0:32768 is ok with 7 open connections.2018-04-05T11:01:19.428637 NOTICE Bolt::Executor: Starting: Drain connections from 0.0.0.0:32768 on ["0.0.0.0:32771"]2018-04-05T11:01:22.553727 NOTICE Bolt::Executor: Finished: Drain connections from 0.0.0.0:32768 on 1 node with 0 failures2018-04-05T11:01:22.555688 NOTICE Bolt::Executor: Starting: Update application for new version on ["0.0.0.0:32768"]2018-04-05T11:01:22.697751 NOTICE Bolt::Executor: Finished: Update application for new version on 1 node with 0 failures2018-04-05T11:01:22.700624 NOTICE Bolt::Executor: Starting: Run Healthcheck for 0.0.0.0:32768 on ["0.0.0.0:32771"]2018-04-05T11:01:22.784539 NOTICE Bolt::Executor: Finished: Run Healthcheck for 0.0.0.0:32768 on 1 node with 0 failures2018-04-05T11:01:22.787086 NOTICE Bolt::Executor: Starting: task my_app::lb on ["0.0.0.0:32771"]2018-04-05T11:01:22.875300 NOTICE Bolt::Executor: Finished: task my_app::lb on 1 node with 0 failuresNotice: Scope(/my_app/plans/deploy.pp, 80): Deploy complete on Target('0.0.0.0:32768', {"connect-timeout"=>10, "tty"=>false, "host-key-check"=>false}).2018-04-05T11:01:22.878628 NOTICE Bolt::Executor: Starting: task my_app::lb on ["0.0.0.0:32771"]2018-04-05T11:01:22.980944 NOTICE Bolt::Executor: Finished: task my_app::lb on 1 node with 0 failuresNotice: Scope(/my_app/plans/deploy.pp, 47): Backend 0.0.0.0:32769 is ok with 9 open connections.2018-04-05T11:01:22.985461 NOTICE Bolt::Executor: Starting: Drain connections from 0.0.0.0:32769 on ["0.0.0.0:32771"]2018-04-05T11:01:26.077658 NOTICE Bolt::Executor: Finished: Drain connections from 0.0.0.0:32769 on 1 node with 0
Jira (BOLT-453) Use more readable log format for the console.
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-453 Use more readable log format for the console. Change By: Alex Dreyer Sprint: Bolt Ready for Grooming Kanban Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 (BOLT-453) Use more readable log format for the console.
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-453
Use more readable log format for the console.
Change By:
Alex Dreyer
The log format makes sense for logging to file but is hard to read on the CLI. Now that we have separate loggers for file and console logging we should use a more succinct format for the console.What is the desired format.Only print the message. Use color to differentiate between error(red), warn(yellow), notice(green) and everything else uncolored.current:{noformat}$ bolt plan run my_app::deploy version=1.0.2 app_servers=app db_server=db lb_server=lb --inventoryfile ./inventory.yaml --modulepath=./modules2018-04-05T11:01:18.711945 NOTICE Bolt::Executor: Starting: Check load before starting deploy on ["0.0.0.0:32771"]2018-04-05T11:01:18.969123 NOTICE Bolt::Executor: Finished: Check load before starting deploy on 1 node with 0 failures2018-04-05T11:01:18.973994 NOTICE Bolt::Executor: Starting: Install 1.0.2 of the application on ["0.0.0.0:32768", "0.0.0.0:32769", "0.0.0.0:32770"]2018-04-05T11:01:19.237311 NOTICE Bolt::Executor: Finished: Install 1.0.2 of the application on 3 nodes with 0 failures2018-04-05T11:01:19.262561 NOTICE Bolt::Executor: Starting: task my_app::lb on ["0.0.0.0:32771"]2018-04-05T11:01:19.413007 NOTICE Bolt::Executor: Finished: task my_app::lb on 1 node with 0 failuresNotice: Scope(/my_app/plans/deploy.pp, 47): Backend 0.0.0.0:32768 is ok with 7 open connections.2018-04-05T11:01:19.428637 NOTICE Bolt::Executor: Starting: Drain connections from 0.0.0.0:32768 on ["0.0.0.0:32771"]2018-04-05T11:01:22.553727 NOTICE Bolt::Executor: Finished: Drain connections from 0.0.0.0:32768 on 1 node with 0 failures2018-04-05T11:01:22.555688 NOTICE Bolt::Executor: Starting: Update application for new version on ["0.0.0.0:32768"]2018-04-05T11:01:22.697751 NOTICE Bolt::Executor: Finished: Update application for new version on 1 node with 0 failures2018-04-05T11:01:22.700624 NOTICE Bolt::Executor: Starting: Run Healthcheck for 0.0.0.0:32768 on ["0.0.0.0:32771"]2018-04-05T11:01:22.784539 NOTICE Bolt::Executor: Finished: Run Healthcheck for 0.0.0.0:32768 on 1 node with 0 failures2018-04-05T11:01:22.787086 NOTICE Bolt::Executor: Starting: task my_app::lb on ["0.0.0.0:32771"]2018-04-05T11:01:22.875300 NOTICE Bolt::Executor: Finished: task my_app::lb on 1 node with 0 failuresNotice: Scope(/my_app/plans/deploy.pp, 80): Deploy complete on Target('0.0.0.0:32768', {"connect-timeout"=>10, "tty"=>false, "host-key-check"=>false}).2018-04-05T11:01:22.878628 NOTICE Bolt::Executor: Starting: task my_app::lb on ["0.0.0.0:32771"]2018-04-05T11:01:22.980944 NOTICE Bolt::Executor: Finished: task my_app::lb on 1 node with 0 failuresNotice: Scope(/my_app/plans/deploy.pp, 47): Backend 0.0.0.0:32769 is ok with 9 open connections.2018-04-05T11:01:22.985461 NOTICE Bolt::Executor: Starting: Drain connections from 0.0.0.0:32769 on ["0.0.0.0:32771"]2018-04-05T11:01:26.077658 NOTICE Bolt::Executor: Finished: Drain connections from 0.0.0.0:32769 on 1 node with 0
Jira (BOLT-453) Use more readable log format for the console.
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-453
Use more readable log format for the console.
Change By:
Alex Dreyer
The log format makes sense for logging to file but is hard to read on the CLI. Now that we have separate loggers for file and console logging we should use a more succinct format for the console.What is the desired format.Only print the message. Use color to differentiate between error(red), warn(yellow), notice(green) everything else uncolored. current:{noformat}$ bolt plan run my_app::deploy version=1.0.2 app_servers=app db_server=db lb_server=lb --inventoryfile ./inventory.yaml --modulepath=./modules2018-04-05T11:01:18.711945 NOTICE Bolt::Executor: Starting: Check load before starting deploy on ["0.0.0.0:32771"]2018-04-05T11:01:18.969123 NOTICE Bolt::Executor: Finished: Check load before starting deploy on 1 node with 0 failures2018-04-05T11:01:18.973994 NOTICE Bolt::Executor: Starting: Install 1.0.2 of the application on ["0.0.0.0:32768", "0.0.0.0:32769", "0.0.0.0:32770"]2018-04-05T11:01:19.237311 NOTICE Bolt::Executor: Finished: Install 1.0.2 of the application on 3 nodes with 0 failures2018-04-05T11:01:19.262561 NOTICE Bolt::Executor: Starting: task my_app::lb on ["0.0.0.0:32771"]2018-04-05T11:01:19.413007 NOTICE Bolt::Executor: Finished: task my_app::lb on 1 node with 0 failuresNotice: Scope(/my_app/plans/deploy.pp, 47): Backend 0.0.0.0:32768 is ok with 7 open connections.2018-04-05T11:01:19.428637 NOTICE Bolt::Executor: Starting: Drain connections from 0.0.0.0:32768 on ["0.0.0.0:32771"]2018-04-05T11:01:22.553727 NOTICE Bolt::Executor: Finished: Drain connections from 0.0.0.0:32768 on 1 node with 0 failures2018-04-05T11:01:22.555688 NOTICE Bolt::Executor: Starting: Update application for new version on ["0.0.0.0:32768"]2018-04-05T11:01:22.697751 NOTICE Bolt::Executor: Finished: Update application for new version on 1 node with 0 failures2018-04-05T11:01:22.700624 NOTICE Bolt::Executor: Starting: Run Healthcheck for 0.0.0.0:32768 on ["0.0.0.0:32771"]2018-04-05T11:01:22.784539 NOTICE Bolt::Executor: Finished: Run Healthcheck for 0.0.0.0:32768 on 1 node with 0 failures2018-04-05T11:01:22.787086 NOTICE Bolt::Executor: Starting: task my_app::lb on ["0.0.0.0:32771"]2018-04-05T11:01:22.875300 NOTICE Bolt::Executor: Finished: task my_app::lb on 1 node with 0 failuresNotice: Scope(/my_app/plans/deploy.pp, 80): Deploy complete on Target('0.0.0.0:32768', {"connect-timeout"=>10, "tty"=>false, "host-key-check"=>false}).2018-04-05T11:01:22.878628 NOTICE Bolt::Executor: Starting: task my_app::lb on ["0.0.0.0:32771"]2018-04-05T11:01:22.980944 NOTICE Bolt::Executor: Finished: task my_app::lb on 1 node with 0 failuresNotice: Scope(/my_app/plans/deploy.pp, 47): Backend 0.0.0.0:32769 is ok with 9 open connections.2018-04-05T11:01:22.985461 NOTICE Bolt::Executor: Starting: Drain connections from 0.0.0.0:32769 on ["0.0.0.0:32771"]2018-04-05T11:01:26.077658 NOTICE Bolt::Executor: Finished: Drain connections from 0.0.0.0:32769 on 1 node with 0
Jira (BOLT-453) Use more readable log format for the console.
Title: Message Title Michael Smith commented on BOLT-453 Re: Use more readable log format for the console. Appended to what? I agree, it's mostly useful if a plan is taking awhile. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 (BOLT-453) Use more readable log format for the console.
Title: Message Title Alex Dreyer commented on BOLT-453 Re: Use more readable log format for the console. That seems like it's only useful if the plan is taking many minutes. Could it be appended? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 (BOLT-453) Use more readable log format for the console.
Title: Message Title Michael Smith commented on BOLT-453 Re: Use more readable log format for the console. I'd maybe include a very short timestamp. Like time since Bolt started (1m12s). Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 (BOLT-453) Use more readable log format for the console.
Title: Message Title Alex Dreyer created an issue Puppet Task Runner / BOLT-453 Use more readable log format for the console. Issue Type: New Feature Assignee: Unassigned Created: 2018/04/04 11:40 AM Priority: Normal Reporter: Alex Dreyer The log format makes sense for logging to file but is hard to read on the CLI. Now that we have separate loggers for file and console logging we should use a more succinct format for the console. What is the desired format. Only print the message. Use color to differentiate between error(red), warn(yellow), notice(green) everything else uncolored. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
