# Setup output to Elasticsearch through Centralized Management **URL:** \ **Category:** Beats\ **Created:** [November 22, 2018, 1:05pm UTC](https://discuss.elastic.co/t/setup-output-to-elasticsearch-through-centralized-management/157881 "2018-11-22T13:05:14Z")\ **Posts on this page:** 1\ **Showing post:** 16
**Author:** ![pierhugues](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pierhugues/32/48383_2.png) [@pierhugues](https://discuss.elastic.co/u/pierhugues)\ **Post date:** [November 26, 2018, 1:14pm UTC](https://discuss.elastic.co/t/setup-output-to-elasticsearch-through-centralized-management/157881/16 "2018-11-26T13:14:39Z")
@mladen Yes the template and the dashboard still requires you to run the setup command to make them available. Its a known issue and we are working on it. > Just one more question, is it possible to use metricbeat key-store and put variable in management.yml file instead of plain text? Yes you can do that, you can add secret to the local keystore and reference them in the config management. We are considering allowing config management to send a keystore to the running instances. FYI: The token that config management is using on the beats to connect to the API is already stored in the keystore. --- _[View the full topic](https://discuss.elastic.co/t/setup-output-to-elasticsearch-through-centralized-management/157881)._