# Kibana Control Visualization Missing Values **URL:** \ **Category:** Kibana\ **Created:** [April 16, 2022, 10:11am UTC](https://discuss.elastic.co/t/kibana-control-visualization-missing-values/302549 "2022-04-16T10:11:27Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![Xadiq](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/xadiq/32/104439_2.png) [@Xadiq](https://discuss.elastic.co/u/Xadiq)\ **Post date:** [April 16, 2022, 10:11am UTC](https://discuss.elastic.co/t/kibana-control-visualization-missing-values/302549/1 "2022-04-16T10:11:27Z")
Hi All, I am facing issue with Kibana Control Visualization. I have field which shows month/year. The index has data from 2014 to 2021 but still the drop down is not showing some values like 12/2021. However if apply the same filet in discover tab - it produces hits. ![image](https://us1.discourse-cdn.com/elastic/original/3X/1/6/166842adde664ad5762eafc4549253313b196d5d.png) ![image](https://us1.discourse-cdn.com/elastic/original/3X/6/a/6a4fb1e1630b81925e7c7214eb3f527f728b4f4e.png) Can you please assist where I am going wrong. Thanks in Advance. ---
**Author:** ![Marius\_Dragomir](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/marius_dragomir/32/42087_2.png) [@Marius\_Dragomir](https://discuss.elastic.co/u/Marius_Dragomir)\ **Post date:** [April 21, 2022, 12:13am UTC](https://discuss.elastic.co/t/kibana-control-visualization-missing-values/302549/2 "2022-04-21T00:13:41Z")
Hello, There are a few common issues that will make that happen and you can find them in the Kibana repo: > > > \*\*Kibana version\*\*: 7.0.0 > > \*\*Elasticsearch version\*\*: 7.0.0 > > \*\*Server OS ver…sion\*\*: CentOS > > \*\*Browser version\*\*: Chrome 80.0.3987.163 > > \*\*Browser OS version\*\*: MacOS > > \*\*Original install method (e.g. download page, yum, from source, etc.)\*\*: download page > > \*\*Description of the problem including expected versus actual behavior\*\*: > > The query produced by a Controls visualization adds, by default, two parameters: > > \`rest\_total\_hits\_as\_int=true\` and \`terminate\_after\` > > This combination of parameters results in the query returning different numbers of results. > > The same query, with \`terminate\_after\` \*but without\* \`rest\_total\_hits\_as\_int=true\` returns all the expected results. > > I'm also getting the expected number of results when the query has \`rest\_total\_hits\_as\_int=true\` \*but doesn't have\* \`terminate\_after\`. > > It seems that the combination of these two options causes the query to terminate earlier: > > Results with \`rest\_total\_hits\_as\_int=true\` \*and\* \`terminate\_after\`: > > \`\`\` > { > "took" : 9, > "timed\_out" : false, > "terminated\_early" : true, > "\_shards" : { > "total" : 22, > "successful" : 22, > "skipped" : 0, > "failed" : 0 > }, > \`\`\` > > Notice the \`terminated\_early: true\` on the result above. > > Compared to the results \*without\* \`rest\_total\_hits\_as\_int=true\` but with \`terminate\_after\`: > > \`\`\` > { > "took" : 4, > "timed\_out" : false, > "\_shards" : { > "total" : 22, > "successful" : 22, > "skipped" : 0, > "failed" : 0 > }, > \`\`\` > > > \*\*Steps to reproduce\*\*: > 1. Create a Controls visualization > 2. Check the query the is issued by Kibana > 3. Try the same query with the mentioned above combination of parameters. > > > \*\*Provide logs and/or server output (if relevant)\*\*: > > I should note that there's nothing relevant on the logs. > > > \## Summary > > This PR adds yml settings for the terminate\_after and timeout para…meters of requests for autocompletion (dropdowns in input control visualizations and suggestions in KQL bar). > > \Screenshot 2019-05-31 at 13 54 04 > > Related: https://github.com/elastic/kibana/issues/17388 > > If a request actually terminates early, a warning symbol is shown in the input control visualization: > > \Screenshot 2019-05-31 at 13 56 27 > > \### Unclear points > > \* \_Location / name of the setting variables\_: Currently, the settings are in the \`kibana\` namespace, because they are consumed in multiple plugins (currently kibana itself and input\_control\_vis). The kibana plugin however is split up into multiple self-containing components and it's not clear where this setting should live > \* \_Wording of the warning message\_: Is copied from an old take on the issue, but might not be ideal > \* \_Warnings for suggestion list\_: If the list of suggestions terminates early, there is no visual indication. The current API of suggestions is not easily extensible (just a simple array of string, no room to carry meta information about the request itself). Is this important? If yes, a separate issue should be created for that. > \* \_Timeout setting\_: It seems like at least under some circumstances, the timeout setting of a request isn't respected but overwritten by the global request timeout of per default 30 seconds. Is a separate timeout for autocomplete requests even necessary? > > \### Checklist > > Use ~~strikethroughs~~ to remove checklist items you don't feel are applicable to this PR. > > \- \[\] This was checked for cross-browser compatibility, \[including a check against IE11\](https://github.com/elastic/kibana/blob/master/CONTRIBUTING.md#cross-browser-compatibility) > \- \[\] Any text added follows \[EUI's writing guidelines\](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes \[i18n support\](https://github.com/elastic/kibana/blob/master/packages/kbn-i18n/README.md) > \- \[\] \[Documentation\](https://github.com/elastic/kibana/blob/master/CONTRIBUTING.md#writing-documentation) was added for features that require explanation or tutorials > \- \[\] \[Unit or functional tests\](https://github.com/elastic/kibana/blob/master/CONTRIBUTING.md#cross-browser-compatibility) were updated or added to match the most common scenarios > \- \[\] This was checked for \[keyboard-only and screenreader accessibility\](https://developer.mozilla.org/en-US/docs/Learn/Tools\_and\_testing/Cross\_browser\_testing/Accessibility#Accessibility\_testing\_checklist) > > \### For maintainers > > \- \[\] This was checked for breaking API changes and was \[labeled appropriately\](https://github.com/elastic/kibana/blob/master/CONTRIBUTING.md#release-notes-process) > \- \[\] This includes a feature addition or change that requires a release note and was \[labeled appropriately\](https://github.com/elastic/kibana/blob/master/CONTRIBUTING.md#release-notes-process) ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [May 19, 2022, 12:14am UTC](https://discuss.elastic.co/t/kibana-control-visualization-missing-values/302549/3 "2022-05-19T00:14:41Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.