Hi Brian,
As of now I am storing the status as log, as I am not getting any
configuration to get the status of the playbook for each node.
Below are the module I am using to store the status of the playbook.
- name: store the information in local
lineinfile:
dest: /tmp/status_files/status-{{ inventory_hostname }}.log
line: '{{ inventory_hostname }} status of {{ inventory_hostname }}
is failed={{rc.failed}} and changed={{rc.changed}}'
create: yes
insertafter: EOF
state: present
#register: line
delegate_to: localhost
Regards
Sumit Sahay
07044112109
On Friday, 31 August 2018 21:06:46 UTC+5:30, Brian Coca wrote:
>
> So there is not 'official' way to do this as `ansible-pull` runs w/o a
> 'controller', it just needs a 'source of playbooks'. It is normally
> git, but could basically be anything.
>
> The simplest setup, if you are already using cron, is to use it's mail
> to facility or aggregate it's logs.
>
> You could change your setup to have a centralized controller via
> Awx/Tower and trigger play runs via it's 'host callback' mechanism.
> this would have a fully centralized execution and reporting on all
> your plays.
>
> Another option is to use Ansible callback plugins, which can integrate
> easily with other tools to do this. They enable you to send playbook
> output to many different services (log aggregation, metrics
> monitoring, ARA, etc).
>
>
>
> ----------
> Brian Coca
>
--
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/ee481597-4698-4791-b8fd-442cd951d012%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
