# Value out of range

**URL:** <https://discuss.elastic.co/t/value-out-of-range/121302>\
**Category:** Beats\
**Tags:** metricbeat\
**Created:** [February 23, 2018, 11:11pm UTC](https://discuss.elastic.co/t/value-out-of-range/121302 "2018-02-23T23:11:52Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![jdambly](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jdambly/32/44286_2.png) [@jdambly](https://discuss.elastic.co/u/jdambly)\
**Post date:** [February 23, 2018, 11:11pm UTC](https://discuss.elastic.co/t/value-out-of-range/121302/1 "2018-02-23T23:11:52Z")

</div>

using metric beat 6.2.1 and logstash 6.2.2 I am getting the following error. I this a metricbeat bug? It seems that the value is too large to fit into a long in ES?

[2018-02-23T23:09:43,469][WARN][logstash.outputs.elasticsearch] Could not index event to Elasticsearch. {:status=\>400, :action=\>["index", {:\_id=\>nil, :\_index=\>"metricbeat-am2-2018.02", :\_type=\>"doc", :\_routing=\>nil}, #LogStash::Event:0x69540279], :response=\>{"index"=\>{"\_index"=\>"metricbeat-am2-2018.02", "\_type"=\>"doc", "\_id"=\>"dBTtxGEBNoUJgeSF8CCY", "status"=\>400, "error"=\>{"type"=\>"mapper\_parsing\_exception", "reason"=\>"failed to parse [system.process.cgroup.memory.kmem\_tcp.limit.bytes]", "caused\_by"=\>{"type"=\>"i\_o\_exception", "reason"=\>"Numeric value (18446744073709551615) out of range of long (-9223372036854775808 - 9223372036854775807)\n at [Source: org.elasticsearch.common.bytes.BytesReference$MarkSupportingStreamInputWrapper@6247f9a3; line: 1, column: 341]"}}}}}  
[2018-02-23T23:09:43,469][WARN][logstash.outputs.elasticsearch] Could not index event to Elasticsearch. {:status=\>400, :action=\>["index", {:\_id=\>nil, :\_index=\>"metricbeat-am2-2018.02", :\_type=\>"doc", :\_routing=\>nil}, #LogStash::Event:0x41d342de], :response=\>{"index"=\>{"\_index"=\>"metricbeat-am2-2018.02", "\_type"=\>"doc", "\_id"=\>"dRTtxGEBNoUJgeSF8CCY", "status"=\>400, "error"=\>{"type"=\>"mapper\_parsing\_exception", "reason"=\>"failed to parse [system.process.cgroup.memory.kmem\_tcp.limit.bytes]", "caused\_by"=\>{"type"=\>"i\_o\_exception", "reason"=\>"Numeric value (18446744073709551615) out of range of long (-9223372036854775808 - 9223372036854775807)\n at [Source: org.elasticsearch.common.bytes.BytesReference$MarkSupportingStreamInputWrapper@6fafce7a; line: 1, column: 341]"}}}}}  
[2018-02-23T23:09:43,469][WARN][logstash.outputs.elasticsearch] Could not index event to Elasticsearch. {:status=\>400, :action=\>["index", {:\_id=\>nil, :\_index=\>"metricbeat-am2-2018.02", :\_type=\>"doc", :\_routing=\>nil}, #LogStash::Event:0xbb8ae0b], :response=\>{"index"=\>{"\_index"=\>"metricbeat-am2-2018.02", "\_type"=\>"doc", "\_id"=\>"dxTtxGEBNoUJgeSF8CCY", "status"=\>400, "error"=\>{"type"=\>"mapper\_parsing\_exception", "reason"=\>"failed to parse [system.process.cgroup.memory.kmem\_tcp.limit.bytes]", "caused\_by"=\>{"type"=\>"i\_o\_exception", "reason"=\>"Numeric value (18446744073709551615) out of range of long (-9223372036854775808 - 9223372036854775807)\n at [Source: org.elasticsearch.common.bytes.BytesReference$MarkSupportingStreamInputWrapper@60aceb3b; line: 1, column: 290]"}}}}}  
[2018-02-23T23:09:43,469][WARN][logstash.outputs.elasticsearch] Could not index event to Elasticsearch. {:status=\>400, :action=\>["index", {:\_id=\>nil, :\_index=\>"metricbeat-am2-2018.02", :\_type=\>"doc", :\_routing=\>nil}, #LogStash::Event:0xc041462], :response=\>{"index"=\>{"\_index"=\>"metricbeat-am2-2018.02", "\_type"=\>"doc", "\_id"=\>"eBTtxGEBNoUJgeSF8CCY", "status"=\>400, "error"=\>{"type"=\>"mapper\_parsing\_exception", "reason"=\>"failed to parse [system.process.cgroup.memory.kmem\_tcp.limit.bytes]", "caused\_by"=\>{"type"=\>"i\_o\_exception", "reason"=\>"Numeric value (18446744073709551615) out of range of long (-9223372036854775808 - 9223372036854775807)\n at [Source: org.elasticsearch.common.bytes.BytesReference$MarkSupportingStreamInputWrapper@48d5c88b; line: 1, column: 341]"}}}}}  
[2018-02-23T23:09:44,184][WARN][logstash.outputs.elasticsearch] Could not index event to Elasticsearch. {:status=\>400, :action=\>["index", {:\_id=\>nil, :\_index=\>"metricbeat-am2-2018.02", :\_type=\>"doc", :\_routing=\>nil}, #LogStash::Event:0x3e49a150], :response=\>{"index"=\>{"\_index"=\>"metricbeat-am2-2018.02", "\_type"

---

<div class="post-metadata">

**Author:** ![andrewkroh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andrewkroh/32/3784_2.png) [@andrewkroh](https://discuss.elastic.co/u/andrewkroh)\
**Post date:** [February 23, 2018, 11:20pm UTC](https://discuss.elastic.co/t/value-out-of-range/121302/2 "2018-02-23T23:20:27Z")

</div>

> [@jdambly](#):
>
> It seems that the value is too large to fit into a long in ES?

That's exactly the case.

You can workaround the issue by dropping the field. I think there's an example in the ticket: [Missing cgroup fields on hardened Debian 8 machines leads to errors · Issue #5854 · elastic/beats · GitHub](https://github.com/elastic/beats/issues/5854)

---

<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:** [March 23, 2018, 11:21pm UTC](https://discuss.elastic.co/t/value-out-of-range/121302/3 "2018-03-23T23:21:02Z")

</div>

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