# NESTされたフィールドに対するwhitelistの適用について

**URL:** <https://discuss.elastic.co/t/nest-whitelist/306282>\
**Category:** 日本語による質問・議論はこちら\
**Created:** [June 3, 2022, 5:14am UTC](https://discuss.elastic.co/t/nest-whitelist/306282 "2022-06-03T05:14:11Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![t-nakata](https://avatars.discourse-cdn.com/v4/letter/t/8491ac/32.png) [@t-nakata](https://discuss.elastic.co/u/t-nakata)\
**Post date:** [June 3, 2022, 7:08am UTC](https://discuss.elastic.co/t/nest-whitelist/306282/5 "2022-06-03T07:08:06Z")

</div>

ありがとうございます。可能であればネストされたフィールド構造は維持したいと考えております。  
下記によるとrubyでも実現できる旨の記載があるので、問い合わせさせて頂きました。頂いた方式も視野に入れつつ検討しようと思います

> [@Prune filter plugin - How whitelist a nested field?](https://discuss.elastic.co/t/prune-filter-plugin-how-whitelist-a-nested-field/255720):
>
> Documentation at has this example and it mentions that it would allow only "msg" through. filter { prune { whitelist\_names =\> ["^msg$"] } } If I have a single record that has "source" =\> { "bytes" =\> 172, "ip" =\> "192.168.56.105", "port" =\> 38996 }, ..... "server" =\> { "bytes" =\> 2400, "ip" =\> "192.168.56.102", "port" =\> 9200 }, Notice how both have the "ip" field. How would I go about on…

---

_[View the full topic](https://discuss.elastic.co/t/nest-whitelist/306282)._