# Ingest node - opposite to Remove Processor?

**URL:** <https://discuss.elastic.co/t/ingest-node-opposite-to-remove-processor/235605>\
**Category:** Elasticsearch\
**Tags:** filebeat\
**Created:** [June 3, 2020, 4:56pm UTC](https://discuss.elastic.co/t/ingest-node-opposite-to-remove-processor/235605 "2020-06-03T16:56:58Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![clarkritchie](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/clarkritchie/32/65755_2.png) [@clarkritchie](https://discuss.elastic.co/u/clarkritchie)\
**Post date:** [June 3, 2020, 4:56pm UTC](https://discuss.elastic.co/t/ingest-node-opposite-to-remove-processor/235605/1 "2020-06-03T16:56:59Z")

</div>

This might be a dumb question, but is there a way to keep only certain fields? Sort of the opposite to the remove processor?

I have a Filebeat on each EC2 server in my ECS cluster configured with:

```auto
filebeat.autodiscover:
  providers:
    - type: docker
      hints.enabled: true
      json.overwrite_keys: true
      json.keys_under_root: true
      json.add_error_key: true

```

My index currently has over 2,900 fields, most of which I have no clue what they are or where they are even coming from, and would like to trim this down to only the fields I am actually interested in.  
So I suspect the `autodiscover` means Filebeat is picking up stuff that I don't care about and forwarding it to ES. Or is there a better solution?

---

<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:** [July 1, 2020, 4:57pm UTC](https://discuss.elastic.co/t/ingest-node-opposite-to-remove-processor/235605/2 "2020-07-01T16:57:04Z")

</div>

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