# Processors are available in metricbeats only or available all beats?

**URL:** <https://discuss.elastic.co/t/processors-are-available-in-metricbeats-only-or-available-all-beats/71801>\
**Category:** Beats\
**Created:** [January 17, 2017, 1:09am UTC](https://discuss.elastic.co/t/processors-are-available-in-metricbeats-only-or-available-all-beats/71801 "2017-01-17T01:09:11Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![kaung](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kaung/32/11165_2.png) [@kaung](https://discuss.elastic.co/u/kaung)\
**Post date:** [January 17, 2017, 1:09am UTC](https://discuss.elastic.co/t/processors-are-available-in-metricbeats-only-or-available-all-beats/71801/1 "2017-01-17T01:09:11Z")

</div>

[Here](https://www.elastic.co/guide/en/beats/metricbeat/5.1/configuration-processors.html), it says libbeat library provides processors - such as drop\_fields, drop\_event. But [beats platform reference](https://www.elastic.co/guide/en/beats/libbeat/current/newbeat-overview.html) also says processors will be available _in the future_. I am confused. Do processors belong to libbeat and can I assume that community beats that implements beats 5.1 framework has processors or only those that implement metricbeat has them?

---

<div class="post-metadata">

**Author:** ![steffens](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/steffens/32/79630_2.png) [@steffens](https://discuss.elastic.co/u/steffens)\
**Post date:** [January 17, 2017, 1:42am UTC](https://discuss.elastic.co/t/processors-are-available-in-metricbeats-only-or-available-all-beats/71801/2 "2017-01-17T01:42:47Z")

</div>

processors are handled by libbeat after an event has been 'published' to libbeat. That is processors are available to all beats. With internally libbeat using a plugin-like architecture to keep track of known processor types, a beat can add a custom processor though (afaik this is currently not the case). [This PR](https://github.com/elastic/beats/pull/3217) even adds experimental (you need to build the beat and the plugin yourself in and for linux) go plugin support for processors.

---

<div class="post-metadata">

**Author:** ![kaung](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kaung/32/11165_2.png) [@kaung](https://discuss.elastic.co/u/kaung)\
**Post date:** [January 17, 2017, 2:13am UTC](https://discuss.elastic.co/t/processors-are-available-in-metricbeats-only-or-available-all-beats/71801/3 "2017-01-17T02:13:03Z")

</div>

👍

---

<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:** [February 7, 2017, 1:09am UTC](https://discuss.elastic.co/t/processors-are-available-in-metricbeats-only-or-available-all-beats/71801/4 "2017-02-07T01:09:20Z")

</div>

This topic was automatically closed after 21 days. New replies are no longer allowed.