# Non-registered extract\_field processor

**URL:** <https://discuss.elastic.co/t/non-registered-extract-field-processor/111448>\
**Category:** Beats\
**Tags:** beats-development\
**Created:** [December 12, 2017, 9:46pm UTC](https://discuss.elastic.co/t/non-registered-extract-field-processor/111448 "2017-12-12T21:46:10Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![MasterCarl](https://avatars.discourse-cdn.com/v4/letter/m/9d8465/32.png) [@MasterCarl](https://discuss.elastic.co/u/MasterCarl)\
**Post date:** [December 12, 2017, 9:46pm UTC](https://discuss.elastic.co/t/non-registered-extract-field-processor/111448/1 "2017-12-12T21:46:10Z")

</div>

I just discovered the [extract\_field processor](https://github.com/elastic/beats/blob/master/libbeat/processors/actions/extract_field.go), which can be used e.g. to extract application instance IDs from log file paths. It might just need some documentation.

However, it is not registered. `This one won't be registered (yet)`  
Is there a reason for that? @exekias

---

<div class="post-metadata">

**Author:** ![exekias](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/exekias/32/28718_2.png) [@exekias](https://discuss.elastic.co/u/exekias)\
**Post date:** [December 14, 2017, 7:36pm UTC](https://discuss.elastic.co/t/non-registered-extract-field-processor/111448/2 "2017-12-14T19:36:25Z")

</div>

Hi @MasterCarl,

Could you explain a little bit why do you want it and how do you plan to use it? Normally we do this kind of processing in the Ingest node or Logstash

---

<div class="post-metadata">

**Author:** ![MasterCarl](https://avatars.discourse-cdn.com/v4/letter/m/9d8465/32.png) [@MasterCarl](https://discuss.elastic.co/u/MasterCarl)\
**Post date:** [December 14, 2017, 9:28pm UTC](https://discuss.elastic.co/t/non-registered-extract-field-processor/111448/3 "2017-12-14T21:28:53Z")

</div>

Hi,

I wanted to extract an instance ID from the path in the exported `source` field on a host running multiple application instances, e.g. `/service/012345/logs/current.log` =\> `012345`.  
I changed my approach to just running one filebeat instance per application and adding static fields based on individual configuration files. Still, I think that having this processor available for general use might be useful. I chose to do this kind of processing on the beat side to minimize transmission overhead.

---

<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:** [January 11, 2018, 9:29pm UTC](https://discuss.elastic.co/t/non-registered-extract-field-processor/111448/4 "2018-01-11T21:29:00Z")

</div>

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