I'm looking into this for 2.9 (with some initial work targetted for 2.8 but that won't be the config portion).
https://github.com/ansible/ansible/issues/49657 -Toshio On Thursday, November 29, 2018 at 4:39:00 AM UTC-8, Jad Baz wrote: > > We can specify a log_path in ansible.cfg > <https://github.com/ansible/ansible/blob/devel/examples/ansible.cfg> which > instructs Ansible to log to a certain file. > Is there a way to specify the verbosity of that logging as well? (The > default is not verbose). > Logging verbosity is not affected by the verbosity from the command line > either. > > If this does not exist, I think it should be a feature request. > It could be quite useful to get more verbose output in the log file. > > This would be especially useful in the following scenario: > You run a play with no/little verbosity and something goes wrong. You run > it again with more verbosity but it doesn't produce the same error. For > some reason it only happens once or now you're getting a different error. > Maybe you made a permanent change in the environment that means you can't > reproduce the same error. If this happens, you're hopeless. > If by default you've configured your log to be verbose, you can not worry > about what you're logging to the command line, get a pretty and uncluttered > output but still have verbose logs for when something goes wrong. > > Thank you > -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/55848d3a-056b-49ad-95a0-591aef18fa1a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
