# Avoid to create new visualizations **URL:** \ **Category:** Beats\ **Tags:** metricbeat\ **Created:** [November 15, 2018, 1:13pm UTC](https://discuss.elastic.co/t/avoid-to-create-new-visualizations/156866 "2018-11-15T13:13:59Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![rschirin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rschirin/32/45283_2.png) [@rschirin](https://discuss.elastic.co/u/rschirin)\ **Post date:** [November 15, 2018, 1:14pm UTC](https://discuss.elastic.co/t/avoid-to-create-new-visualizations/156866/1 "2018-11-15T13:14:00Z")
Hi all, I'm trying to use default Metricbeat visualizations and dashboard of System module. Working just with one cluster I have not any issue but if I start to play with another cluster (i.e. another environment), I would like to avoid to import new visualizations (I know that I must have a different dashboard to manage different cluster). do you have any tips? is there a way to generate randomly the `id`'s value of every `visualization`? or is there a smart way to manage it? ---
**Author:** ![jsoriano](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jsoriano/32/27920_2.png) [@jsoriano](https://discuss.elastic.co/u/jsoriano)\ **Post date:** [November 15, 2018, 2:42pm UTC](https://discuss.elastic.co/t/avoid-to-create-new-visualizations/156866/2 "2018-11-15T14:42:18Z")
Hi @rschirin, I think I don't completely understand your problem 🤔 By having two clusters, do you mean that you have two different groups of hosts? What is the problem with them? are they using different metricbeat versions? or what is the reason you want to setup the visualizations again? ---
**Author:** ![rschirin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rschirin/32/45283_2.png) [@rschirin](https://discuss.elastic.co/u/rschirin)\ **Post date:** [November 15, 2018, 4:13pm UTC](https://discuss.elastic.co/t/avoid-to-create-new-visualizations/156866/3 "2018-11-15T16:13:35Z")
for sure my question was not so clear. I will try to go deeper. I have 2 servers, one for _Test Environment_ and one for _Production Environment_. I want to collect their system metrics, so I decided to use `Metricbeat` with System module (just to start). I configured `metricbeat.yml` for _Test Env_ and started `Metricbeat`. I allowed also the import procedure into Kibana. After that I configured also the other `Metricbeat`, more or less in the same way but different `index.template` value. When I started the second `Metricbeat` (_Prod Env_), every visualizations and dashboard are overwritten. so, is there a way to avoid it? What I would like to get at the end is visualizations and dashboards for _Test Env_ and visualizations and dashboards for _Prod Env_. ---
**Author:** ![jsoriano](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jsoriano/32/27920_2.png) [@jsoriano](https://discuss.elastic.co/u/jsoriano)\ **Post date:** [November 16, 2018, 10:02am UTC](https://discuss.elastic.co/t/avoid-to-create-new-visualizations/156866/4 "2018-11-16T10:02:14Z")
What are the settings you are changing to modify the index template? You could try to set `setup.dashboards.index` to some pattern that matches the indexes names of both environments (for example setting it to `metricbeat-*` if your indexes are `metricbeat-prod-...` and `metricbeat-test-...`. This way you'd still have an only set of dashboards, but they could be used for both sets of indexes. At the moment there is no way to modify the dashboards ids, so you cannot have dashboards of different versions or with different patterns. One thing you can try is [Kibana Spaces](https://www.elastic.co/guide/en/kibana/6.5/xpack-spaces.html), a new feature introduced in Kibana 6.5.0 that allows to have different environments for dashboards and visualizations, so you can have the same ids in different Spaces. To use them with Beats, add the base URL to the `setup.kibana.host` setting. For example if you have an environment named `test` on a Kibana instance in `http://kibana.example.com:5601` the config would be: ```auto setup.kibana.host: 'http://kibana.example.com:5601/s/test' ``` Kibana Spaces requires [x-pack basic](https://www.elastic.co/subscriptions), that is included in the [default packages](https://www.elastic.co/downloads/kibana). ---
**Author:** ![rschirin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rschirin/32/45283_2.png) [@rschirin](https://discuss.elastic.co/u/rschirin)\ **Post date:** [November 16, 2018, 6:42pm UTC](https://discuss.elastic.co/t/avoid-to-create-new-visualizations/156866/5 "2018-11-16T18:42:31Z")
@jsoriano thank you . I will try Spaces feature even if I'm facing a creation issue in this moment. If I will not use it, have I to create import every time dashboard and visualizations with different `_id` and `name`, right? ---
**Author:** ![jsoriano](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jsoriano/32/27920_2.png) [@jsoriano](https://discuss.elastic.co/u/jsoriano)\ **Post date:** [November 19, 2018, 10:50am UTC](https://discuss.elastic.co/t/avoid-to-create-new-visualizations/156866/6 "2018-11-19T10:50:51Z")
> [@rschirin](#): > > If I will not use it, have I to create import every time dashboard and visualizations with different `_id` and `name` , right? If you want to have multiple versions of the same dashboards, or the same dashboards with different indexes, then yes you'd need to use different ids. But changing dashboard names or ids is not currently supported by beats, you'd need to modify the ids on your own. You may also want to [open an enhancement request](https://github.com/elastic/beats/issues/new?labels=&template=feature-request.md) for your use case. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [December 17, 2018, 10:50am UTC](https://discuss.elastic.co/t/avoid-to-create-new-visualizations/156866/7 "2018-12-17T10:50:53Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.