# Metricbeat 5.0.0-alpha5 processors range works other than documented

**URL:** <https://discuss.elastic.co/t/metricbeat-5-0-0-alpha5-processors-range-works-other-than-documented/57769>\
**Category:** Beats\
**Tags:** metricbeat\
**Created:** [August 11, 2016, 8:15am UTC](https://discuss.elastic.co/t/metricbeat-5-0-0-alpha5-processors-range-works-other-than-documented/57769 "2016-08-11T08:15:38Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![kaem2111](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kaem2111/32/24961_2.png) [@kaem2111](https://discuss.elastic.co/u/kaem2111)\
**Post date:** [August 11, 2016, 8:15am UTC](https://discuss.elastic.co/t/metricbeat-5-0-0-alpha5-processors-range-works-other-than-documented/57769/1 "2016-08-11T08:15:38Z")

</div>

Hello,

I use metricbeat 5.0.0-alpha5 with processors and range.  
I tried:

> ```
> processors:
> - drop_event:
> when:
> range:
> lte:
> system.process.cpu.total.pct: 0.0001
> 
> ```

which leads to configuration error:

> 2016/08/11 07:51:14.398256 beat.go:174: INFO Setup Beat: metricbeat; Version: 5.0.0-alpha5  
> 2016/08/11 07:51:14.398327 condition.go:488: ERR Failed to initialize lookup condition: unexpected field pct  
> 2016/08/11 07:51:14.398350 beat.go:284: CRIT Exiting: error initializing processors: unexpected field pct

I tried:

> ```
> processors:
> - drop_event:
> when:
> range:
> system.process.cpu.total.pct.lte: 0.0001
> 
> ```

which has no configuration error and leads to:

> 2016-08-11T09:55:05+02:00 DBG New condition range: map[system.process.cpu.total.pct:\<= 0.0001]  
> ..  
> 2016-08-11T12:05:42+02:00 DBG Drop event {

which finally works.  
So maybe documentation need to be updated.

---

<div class="post-metadata">

**Author:** ![monica](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/monica/32/3696_2.png) [@monica](https://discuss.elastic.co/u/monica)\
**Post date:** [August 11, 2016, 11:02am UTC](https://discuss.elastic.co/t/metricbeat-5-0-0-alpha5-processors-range-works-other-than-documented/57769/2 "2016-08-11T11:02:31Z")

</div>

Thank you @kaem2111 for reporting this issue. Indeed it's a bug in the documentation, and we will fix it as soon as possible. For more details about the conditions, you can also check the [meta issue](https://github.com/elastic/beats/issues/1447), that confirms the format of the `range` condition.

---

<div class="post-metadata">

**Author:** ![monica](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/monica/32/3696_2.png) [@monica](https://discuss.elastic.co/u/monica)\
**Post date:** [August 11, 2016, 11:45am UTC](https://discuss.elastic.co/t/metricbeat-5-0-0-alpha5-processors-range-works-other-than-documented/57769/3 "2016-08-11T11:45:41Z")

</div>

Here is the PR that solves the issue: [https://github.com/elastic/beats/pull/2241](https://github.com/elastic/beats/pull/2241)

---

<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:** [September 1, 2016, 8:15am UTC](https://discuss.elastic.co/t/metricbeat-5-0-0-alpha5-processors-range-works-other-than-documented/57769/4 "2016-09-01T08:15:52Z")

</div>

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