# Twitter Input: Controlling Fields to Ingest

**URL:** <https://discuss.elastic.co/t/twitter-input-controlling-fields-to-ingest/125844>\
**Category:** Logstash\
**Created:** [March 28, 2018, 3:32am UTC](https://discuss.elastic.co/t/twitter-input-controlling-fields-to-ingest/125844 "2018-03-28T03:32:48Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![wwalker](https://avatars.discourse-cdn.com/v4/letter/w/43a26b/32.png) [@wwalker](https://discuss.elastic.co/u/wwalker)\
**Post date:** [March 28, 2018, 3:32am UTC](https://discuss.elastic.co/t/twitter-input-controlling-fields-to-ingest/125844/1 "2018-03-28T03:32:48Z")

</div>

The Twitter input will create well over 1k fields if left to its own devices. I have a mutate in my pipeline to remove a few hundred, unfortunately, it's kind of a resource hog to do it this way. Is there another, more effective way to control what fields are pulled/processed? I feel like this is gonna be a stupid easy thing to fix...

---

<div class="post-metadata">

**Author:** ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)\
**Post date:** [April 2, 2018, 9:50am UTC](https://discuss.elastic.co/t/twitter-input-controlling-fields-to-ingest/125844/2 "2018-04-02T09:50:27Z")

</div>

Have a look a the prune filter.

---

<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:** [April 30, 2018, 9:51am UTC](https://discuss.elastic.co/t/twitter-input-controlling-fields-to-ingest/125844/3 "2018-04-30T09:51:34Z")

</div>

Closed on April 30, 2018, 9:51am UTC

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