3

Instead of the single log file defined in log_path, I want to have separate log files per playbook run in Ansible.

As far as I know there is no built-in way to do that. So I am looking for clever "hacks".

More specifically, I want after a playbook is ran a log file to be generated in the format [playbook name].[date].log

I found this thread in SO but it doesn't meet my needs. The alias would be a solution if I could pass somehow the playbook name dynamically, not only the date. The lookup solution would be ok if I could copy only the relevant part from the main log file without all the history up until the moment of the copy. Additionally, if you have many playbooks running in parallel I don't know how good this method will work.

Any clues / ideas? What I thought is creating a shell script that would be called inside a playbook to somehow "extract" the relevant entries from the main log and create a separate one. But I believe I am making it too complex.

Community
  • 1
  • 1
Cobra Kai Dojo
  • 1,018
  • 2
  • 12
  • 25

2 Answers2

10

Be sure to comment out the log_path option in ansible.cfg.

create a wrapper shell script: ansible-playbook-wrapper.sh

#!/bin/bash

export ANSIBLE_LOG_PATH=/var/log/ansible/playbook_$(echo $1 | cut -d . -f 1).log
ansible-playbook $@

alias ansible-playbook to run the wrapper script instead:

alias ansible-playbook="/path/to/ansible-playbook-wrapper.sh"

create a log directory and open up permissions so all users (or perhaps all ansible users) can write to it:

sudo mkdir /var/log/ansible
sudo chmod 777 /var/log/ansible

Now when you run ansible-playbook dns_server.yml -u cobra -k you will see the following:

[cobra@ansible ~]$ ls /var/log/ansible
playbook-dns_server.log
playbook-some_other_playbook.log
playbook-even_more_plays.log
Dave Snigier
  • 2,574
  • 3
  • 21
  • 29
  • this was working for me, but now ansible no longer recogonizes some of my arguments. I tried killing the subshells for my user account, then ran ```exec bash``` after making changes to .bashrc. This worked temporarily, but now ansible is back to not recognized args that had worked before using the wrapper. – ficestat Aug 25 '20 at 22:55
  • You need to tweak the order of parameters to make playbook.yml the first argumet. – Favo Yang Oct 16 '20 at 12:10
1

Little late but maybe help someone else.

ANSIBLE_LOG_PATH=test.log ansible-playbook playbook.yml

or to answer OP question:

ANSIBLE_LOG_PATH=playbook.$(date +%m%d%Y).log ansible-playbook playbook.yml

Carl Andrews
  • 61
  • 1