# Filebeat pipeline setup for system module ignores var.convert\_timezone: true?

**URL:** <https://discuss.elastic.co/t/filebeat-pipeline-setup-for-system-module-ignores-var-convert-timezone-true/181456>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [May 16, 2019, 5:17pm UTC](https://discuss.elastic.co/t/filebeat-pipeline-setup-for-system-module-ignores-var-convert-timezone-true/181456 "2019-05-16T17:17:27Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![pdizz](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pdizz/32/45941_2.png) [@pdizz](https://discuss.elastic.co/u/pdizz)\
**Post date:** [May 16, 2019, 7:32pm UTC](https://discuss.elastic.co/t/filebeat-pipeline-setup-for-system-module-ignores-var-convert-timezone-true/181456/2 "2019-05-16T19:32:56Z")

</div>

So it looks like the filebeat setup command is loading filebeat.yml but ignoring the module configs when setting up the pipeline.

If you configure `var.convert_timezone=true` in filebeat.yaml,

or add it to the setup command like this `filebeat setup --pipelines --modules system -E output.logstash.enabled=false -E output.elasticsearch.hosts=['localhost:9200'] -M system.auth.var.convert_timezone=true -M system.syslog.var.convert_timezone=true`

the ingest pipeline is created as expected

---

_[View the full topic](https://discuss.elastic.co/t/filebeat-pipeline-setup-for-system-module-ignores-var-convert-timezone-true/181456)._