# Expected numeric type on field but got \[keyword\]

**URL:** <https://community.graylog.org/t/expected-numeric-type-on-field-but-got-keyword/21031>\
**Category:** Graylog Central (peer support)\
**Created:** [August 30, 2021, 11:50pm UTC](https://community.graylog.org/t/expected-numeric-type-on-field-but-got-keyword/21031 "2021-08-30T23:50:03Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![wobble\_butt](https://avatars.discourse-cdn.com/v4/letter/w/9de0a6/32.png) [@wobble\_butt](https://community.graylog.org/u/wobble_butt)\
**Post date:** [August 31, 2021, 3:53am UTC](https://community.graylog.org/t/expected-numeric-type-on-field-but-got-keyword/21031/3 "2021-08-31T03:53:16Z")

</div>

Thank you @gsmith, I was hoping to fix it using pipelines, is there no other way than mapping? Here are 2 similar answers which I’m basing this on:  
[2017](https://community.graylog.org/t/expected-numeric-type-on-field-flag-but-got-keyword/3541/2)  
[2019](https://community.graylog.org/t/expected-numeric-type-on-field-application-but-got-keyword/9483/2)

The GELF payload is in the “message” field, and I use an JSON extractor to create all the other fields. Even though the monthly\_sales value is sent as a float on my end, I assumed the JSON extractor was the one turning it into a string.

So after building the pipeline and forcing this field to be numeric, it’s very disheartening to see the avg() function in the charts still throwing this error.

Does mapping apply to this situation since the field is created by the extractor? Seems like i’m missing something really simple.

---

_[View the full topic](https://community.graylog.org/t/expected-numeric-type-on-field-but-got-keyword/21031)._