# Control visualization **URL:** \ **Category:** Kibana\ **Created:** [May 5, 2021, 9:26am UTC](https://discuss.elastic.co/t/control-visualization/272158 "2021-05-05T09:26:13Z")\ **Posts on this page:** 11\ **Page:** 1
**Author:** ![graimato](https://avatars.discourse-cdn.com/v4/letter/g/9e8a1a/32.png) [@graimato](https://discuss.elastic.co/u/graimato)\ **Post date:** [May 5, 2021, 9:26am UTC](https://discuss.elastic.co/t/control-visualization/272158/1 "2021-05-05T09:26:13Z")
Dear all, it is possible to use Control visualization to filter on group of parameters? Suppose that there are: - Test - Prod It is possible to have Control to choose Test or Prod and have all information about host.hostname: ServerTest\* or host.hostname: ServerProd\*? Thank for your time ---
**Author:** ![Wolfram\_Haussig](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/wolfram_haussig/32/70528_2.png) [@Wolfram\_Haussig](https://discuss.elastic.co/u/Wolfram_Haussig)\ **Post date:** [May 6, 2021, 6:55am UTC](https://discuss.elastic.co/t/control-visualization/272158/2 "2021-05-06T06:55:34Z")
Hi, Yes, you can - you need a control viz with 2 separate option lists(one for Test/Prod and one for the servers). For the server control you configure the environment as parent: ![image](https://us1.discourse-cdn.com/elastic/original/3X/d/7/d7ad5955b65a47ec657a9174113e0f7de0cec126.png) This leads to the following result: ![image](https://us1.discourse-cdn.com/elastic/original/3X/7/1/716926fd1df8818c5cf9c02792367a79f4f3c855.png) When you select an environment the hostname becomes active and provides you with a list of hosts to choose from. Best regards Wolfram ---
**Author:** ![graimato](https://avatars.discourse-cdn.com/v4/letter/g/9e8a1a/32.png) [@graimato](https://discuss.elastic.co/u/graimato)\ **Post date:** [May 6, 2021, 9:01am UTC](https://discuss.elastic.co/t/control-visualization/272158/3 "2021-05-06T09:01:45Z")
Thanks @Wolfram_Haussig for your quick response, I understand the idea and I think that It can works, but do you think that I have to create the environment field using tags or fields.env from metricbeat.yml file configuration? thanks so much ---
**Author:** ![Wolfram\_Haussig](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/wolfram_haussig/32/70528_2.png) [@Wolfram\_Haussig](https://discuss.elastic.co/u/Wolfram_Haussig)\ **Post date:** [May 6, 2021, 9:21am UTC](https://discuss.elastic.co/t/control-visualization/272158/4 "2021-05-06T09:21:30Z")
You need to use the fields.env option as tags cannot create keys with values as it is an array of keywords(see definition [here](https://www.elastic.co/guide/en/ecs/current/ecs-base.html#field-tags)). It _could_ be possible to use the tags (though I have not tried it myself) by specifying `tags` as field name for the environment but if there are other tags added to the event those would show up as well(e.g. grok\_parse\_failure, ...). ---
**Author:** ![graimato](https://avatars.discourse-cdn.com/v4/letter/g/9e8a1a/32.png) [@graimato](https://discuss.elastic.co/u/graimato)\ **Post date:** [May 6, 2021, 9:36am UTC](https://discuss.elastic.co/t/control-visualization/272158/5 "2021-05-06T09:36:21Z")
thanks @Wolfram_Haussig , I tried with tags and with fields.env I have correct data into discover ex: fields.env: testenv but when I try to create the first option list I do not see env Field thanks so much ---
**Author:** ![Wolfram\_Haussig](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/wolfram_haussig/32/70528_2.png) [@Wolfram\_Haussig](https://discuss.elastic.co/u/Wolfram_Haussig)\ **Post date:** [May 6, 2021, 9:37am UTC](https://discuss.elastic.co/t/control-visualization/272158/6 "2021-05-06T09:37:37Z")
Have you updated the kibana index pattern? ---
**Author:** ![graimato](https://avatars.discourse-cdn.com/v4/letter/g/9e8a1a/32.png) [@graimato](https://discuss.elastic.co/u/graimato)\ **Post date:** [May 6, 2021, 9:44am UTC](https://discuss.elastic.co/t/control-visualization/272158/7 "2021-05-06T09:44:03Z")
> [@Wolfram\_Haussig](#): > > kibana ind Yes I did but I think that the operation was slow now I have field Thanks so much for your help ---
**Author:** ![graimato](https://avatars.discourse-cdn.com/v4/letter/g/9e8a1a/32.png) [@graimato](https://discuss.elastic.co/u/graimato)\ **Post date:** [May 6, 2021, 9:56am UTC](https://discuss.elastic.co/t/control-visualization/272158/8 "2021-05-06T09:56:43Z")
No @Wolfram_Haussig sorry for the previous message. I have the field in to discovery as string but I continue to do not see field in visualization Field. It is strange ---
**Author:** ![Wolfram\_Haussig](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/wolfram_haussig/32/70528_2.png) [@Wolfram\_Haussig](https://discuss.elastic.co/u/Wolfram_Haussig)\ **Post date:** [May 6, 2021, 10:28am UTC](https://discuss.elastic.co/t/control-visualization/272158/9 "2021-05-06T10:28:53Z")
Can you please check what the index pattern page says about this field? I have just checked the documentation here: [https://www.elastic.co/guide/en/kibana/current/enhance-dashboards.html](https://www.elastic.co/guide/en/kibana/current/enhance-dashboards.html) > The dropdown menu is dynamically populated with the results of a terms aggregation My guess is that the field is not marked as aggregatable in the index pattern. more than likely, the field was automatically mapped as text instead of keyword which does not support aggregation. ---
**Author:** ![graimato](https://avatars.discourse-cdn.com/v4/letter/g/9e8a1a/32.png) [@graimato](https://discuss.elastic.co/u/graimato)\ **Post date:** [May 6, 2021, 10:37am UTC](https://discuss.elastic.co/t/control-visualization/272158/10 "2021-05-06T10:37:59Z")
Thanks so much for your help, I'll refresh the index I'm sure that your solution is perfect for my problem thanks so much @Wolfram_Haussig ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [June 3, 2021, 10:38am UTC](https://discuss.elastic.co/t/control-visualization/272158/11 "2021-06-03T10:38:22Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.