# Filebeat setup is not idempotent **URL:** \ **Category:** Beats\ **Tags:** filebeat\ **Created:** [December 10, 2018, 4:11pm UTC](https://discuss.elastic.co/t/filebeat-setup-is-not-idempotent/160211 "2018-12-10T16:11:57Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![ORich](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/orich/32/21675_2.png) [@ORich](https://discuss.elastic.co/u/ORich)\ **Post date:** [December 10, 2018, 4:11pm UTC](https://discuss.elastic.co/t/filebeat-setup-is-not-idempotent/160211/1 "2018-12-10T16:11:57Z")
According to Filebeat documentation : "the `setup` command loads the recommended index template for writing to Elasticsearch and deploys the sample dashboards (if available) for visualizing the data in Kibana. This is a one-time setup step." From a Devops perspective, it looks like the command 'filebeat setup' is not idempotent i.e. the whole setup is rerun each time. Is there a way to check if index and dashboard are already setup in order to decide to run filebeat setup or not ? Thanks for your support. Best Regards. ---
**Author:** ![ORich](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/orich/32/21675_2.png) [@ORich](https://discuss.elastic.co/u/ORich)\ **Post date:** [December 13, 2018, 8:44am UTC](https://discuss.elastic.co/t/filebeat-setup-is-not-idempotent/160211/2 "2018-12-13T08:44:56Z")
As a a workaround, I do now load the dashboard by enabling the `setup.dashboards` section of the `metricbeat.yml` config file. This way, the loading is idempotent unlike the CLI setup command. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [January 10, 2019, 8:44am UTC](https://discuss.elastic.co/t/filebeat-setup-is-not-idempotent/160211/3 "2019-01-10T08:44:57Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.