# 1.8 update news: By popular demand, no\_log True has increased censorship

**URL:** <https://forum.ansible.com/t/1-8-update-news-by-popular-demand-no-log-true-has-increased-censorship/15925>\
**Category:** Ansible Project\
**Created:** [August 12, 2014, 5:37pm UTC](https://forum.ansible.com/t/1-8-update-news-by-popular-demand-no-log-true-has-increased-censorship/15925 "2014-08-12T17:37:29Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Michael\_DeHaan1](https://avatars.discourse-cdn.com/v4/letter/m/5e9695/32.png) [@Michael\_DeHaan1](https://forum.ansible.com/u/Michael_DeHaan1)\
**Post date:** [August 12, 2014, 5:37pm UTC](https://forum.ansible.com/t/1-8-update-news-by-popular-demand-no-log-true-has-increased-censorship/15925/1 "2014-08-12T17:37:29Z")

</div>

Previously in ansible the no\_log: True attribute on a task or a play hides  
any logging from hitting syslog on the remote system.

In addition to this, on 1.8, I’ve also implemented a much requested new  
feature that also hides this from callbacks, such that the data as shown  
by -v, or passed to any callback plugins, is censored.

Try it by adding no\_log: True to any task.

(I’ve also added this to the FAQ documentation, which is not pushed just yet)