# Hide some of "available fields" in Kibana Discover
**URL:** https://discuss.elastic.co/t/hide-some-of-available-fields-in-kibana-discover/249088
**Category:** Kibana
**Created:** [September 18, 2020, 10:47am UTC](https://discuss.elastic.co/t/hide-some-of-available-fields-in-kibana-discover/249088 "2020-09-18T10:47:29Z")
**Posts on this page:** 6
**Page:** 1
### Author:  [@a1tus](https://discuss.elastic.co/u/a1tus)
#### Post date: [September 18, 2020, 10:47am UTC](https://discuss.elastic.co/t/hide-some-of-available-fields-in-kibana-discover/249088/1 "2020-09-18T10:47:30Z")
Hello.
We've structured our logs so that we have only a few indexed and searchable fields and all the rest goes into "extra" field that is not indexed and can't be searched (so we put there arbitrary keys and values that can also be deeply nested).
Everything is fine but all of these "extra" garbage is shown in "available fields" section and makes all the page hard to use sometimes.
"Filter by type" feature helps a bit (you can choose "searchable" there) but it is not saved and needs to be clicked manually every time.
I've tried to use "source filters" according like in this question:
> [@Kibana discover shows disabled fields in "available fields" list](https://discuss.elastic.co/t/kibana-discover-shows-disabled-fields-in-available-fields-list/246806):
>
> I specifically used index mapping to disable some high cardinality fields: "siteEntity": { "properties": { "defaultPlacementsForMediaType": { "type": "object", "enabled": false } } } When I look at index pattern in Kibana, the field defaultPlacementsForMediaType is not in there, as expected. However, Kibana discover is still trying to load every distinct value for that field and show in available fiel…
and field really disappears from available fields but it also disappears from the data in table itself which is not acceptable.
Is there any way to exclude some particular field just from there (or even whitelist what can be shown there)?
---
### Author:  [@matw](https://discuss.elastic.co/u/matw)
#### Post date: [September 18, 2020, 4:25pm UTC](https://discuss.elastic.co/t/hide-some-of-available-fields-in-kibana-discover/249088/2 "2020-09-18T16:25:20Z")
Hi and welcome to our community
Thank you for your feedback, saving the last settings for the fields filter is a neat idea, and I've been adding a feature request for this
>
>
> For users that are specially interested in certain field types it would be useful to persist their last used filter settings...
Currently it's not possible to hide those fields, but this is discussed, so this is welcome feedback for us, thx.
Best,
Matthias
---
### Author:  [@a1tus](https://discuss.elastic.co/u/a1tus)
#### Post date: [September 18, 2020, 7:03pm UTC](https://discuss.elastic.co/t/hide-some-of-available-fields-in-kibana-discover/249088/3 "2020-09-18T19:03:57Z")
I've subscribed to this issue, thanks.
> [@matw](#):
>
> Currently it's not possible to hide those fields, but this is discussed
Is this discussion public (maybe on github too)? I would track it then too.
Both solutions will do the trick though so let's see what happens =)
---
### Author:  [@matw](https://discuss.elastic.co/u/matw)
#### Post date: [September 18, 2020, 7:32pm UTC](https://discuss.elastic.co/t/hide-some-of-available-fields-in-kibana-discover/249088/4 "2020-09-18T19:32:39Z")
Not yet, but there's an issue for a new field type to come : runtime fields, and this will lead to changes in this component: [https://github.com/elastic/kibana/issues/77107](https://github.com/elastic/kibana/issues/77107)
---
### Author:  [@matw](https://discuss.elastic.co/u/matw)
#### Post date: [September 18, 2020, 7:35pm UTC](https://discuss.elastic.co/t/hide-some-of-available-fields-in-kibana-discover/249088/5 "2020-09-18T19:35:21Z")
Of course you could also open a feature request.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [October 16, 2020, 7:35pm UTC](https://discuss.elastic.co/t/hide-some-of-available-fields-in-kibana-discover/249088/6 "2020-10-16T19:35:47Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.