# Syslog facility

**URL:** <https://forum.ansible.com/t/syslog-facility/11982>\
**Category:** Ansible Project\
**Created:** [October 16, 2012, 12:03am UTC](https://forum.ansible.com/t/syslog-facility/11982 "2012-10-16T00:03:42Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Aleksej\_Romanov](https://avatars.discourse-cdn.com/v4/letter/a/278dde/32.png) [@Aleksej\_Romanov](https://forum.ansible.com/u/Aleksej_Romanov)\
**Post date:** [October 16, 2012, 12:03am UTC](https://forum.ansible.com/t/syslog-facility/11982/1 "2012-10-16T00:03:42Z")

</div>

I would like to set Syslog facility for log entries that Ansible write  
(so I can manage destination and filters). Thought about adding an  
option to config file. But library/async\_wrapper and library/fireball  
are uploaded to remote hosts (and so looks like don't have access to  
configuration, right?). Is there any handy way to pass config data to  
modules? Trying to pass syslog facility as option for this two modules  
seems a bit wrong for me.

---

<div class="post-metadata">

**Author:** ![Michael\_DeHaan](https://avatars.discourse-cdn.com/v4/letter/m/c4cdca/32.png) [@Michael\_DeHaan](https://forum.ansible.com/u/Michael_DeHaan)\
**Post date:** [October 16, 2012, 12:19am UTC](https://forum.ansible.com/t/syslog-facility/11982/2 "2012-10-16T00:19:12Z")

</div>

Python module files are templated prior to transfer, so this is pretty  
easy to pass in by adding a new variable to each module prior to  
transfer.

How about filing an idea ticket so we can see about doing this for 0.9.

--Michael