# UI for search

**URL:** https://discuss.elastic.co/t/ui-for-search/214042
**Category:** Kibana
**Created:** [January 7, 2020, 11:54am UTC](https://discuss.elastic.co/t/ui-for-search/214042 "2020-01-07T11:54:36Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![rubpa](https://avatars.discourse-cdn.com/v4/letter/r/b5e925/32.png) [@rubpa](https://discuss.elastic.co/u/rubpa)
#### Post date: [January 7, 2020, 11:54am UTC](https://discuss.elastic.co/t/ui-for-search/214042/1 "2020-01-07T11:54:36Z")

</div>

We have an existing MySQL based application which has data over several years. We have created meaningful SQL queries (i.e. join/flatten the data) and indexed that data into elasticsearch. And we want to offer this data for free-form or structured search to our users.

I chose to use Kibana (v7.4.2 currently) [data tables](https://www.elastic.co/guide/en/kibana/7.4/data-table.html) to display the search results. See attached screenshots - the 3 visible tables are aggregations of the data on 3 different parameters which are meaningful for us - there are more visualizations below these 3 tables.

One challenge I face is the scrollbars that appears and disappear based on the search results. It gives a feeling of an unprofessional GUI. If I choose a large height for the visualization on the dashboard - I end up with too much whitespace lots of times. Too little height and there is a scrollbar most of the times. I haven't found a good balance since our data has single line text as well several lines text.

Do you have any suggestions or ideas to build a search UI using Kibana? A dynamically adapting data-table would be nice but Kibana's dashboard is fundamentally built around fixed areas for each widget.

 ![kibana-scrolls1](https://us1.discourse-cdn.com/elastic/original/3X/2/4/243f6e683cdd044180422a63ecc5efbfc8656d91.jpeg)

 ![kibana-scrolls2](https://us1.discourse-cdn.com/elastic/original/3X/a/7/a738bc9f97966310a2bf3992ae42ede320305815.jpeg)

---

<div class="post-metadata">

### Author: ![tsullivan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tsullivan/32/31077_2.png) [@tsullivan](https://discuss.elastic.co/u/tsullivan)
#### Post date: [January 8, 2020, 8:09pm UTC](https://discuss.elastic.co/t/ui-for-search/214042/2 "2020-01-08T20:09:41Z")

</div>

I think this would be a good feature request for Kibana. Right now, the dashboard doesn't allow for panel height to be dynamically calculated based on the size of the content in the panel. Maybe that could be an option for the dashboard. Saved search panels are embeddable in other apps as well, so a solution wouldn't just be limited to Dashboard options.

> **[Build software better, together](https://github.com/elastic/kibana/issues/new?template=Feature_request.md)**
>
> GitHub is where people build software. More than 40 million people use GitHub to discover, fork, and contribute to over 100 million projects.

---

<div class="post-metadata">

### Author: ![rubpa](https://avatars.discourse-cdn.com/v4/letter/r/b5e925/32.png) [@rubpa](https://discuss.elastic.co/u/rubpa)
#### Post date: [January 9, 2020, 5:26am UTC](https://discuss.elastic.co/t/ui-for-search/214042/3 "2020-01-09T05:26:20Z")

</div>

Done - [https://github.com/elastic/kibana/issues/54326](https://github.com/elastic/kibana/issues/54326)

Any idea on how I can use Kibana or the elastic stack for my use case more effectively until then?

---

<div class="post-metadata">

### Author: ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)
#### Post date: [February 6, 2020, 5:26am UTC](https://discuss.elastic.co/t/ui-for-search/214042/4 "2020-02-06T05:26:24Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
