# Netflow.conn\_id out of range?

**URL:** <https://discuss.elastic.co/t/netflow-conn-id-out-of-range/113363>\
**Category:** Logstash\
**Created:** [December 27, 2017, 8:47pm UTC](https://discuss.elastic.co/t/netflow-conn-id-out-of-range/113363 "2017-12-27T20:47:59Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Diogo](https://avatars.discourse-cdn.com/v4/letter/d/ea666f/32.png) [@Diogo](https://discuss.elastic.co/u/Diogo)\
**Post date:** [December 27, 2017, 8:47pm UTC](https://discuss.elastic.co/t/netflow-conn-id-out-of-range/113363/1 "2017-12-27T20:47:59Z")

</div>

Hi!

After running Logstash with the Netflow module for a little less than two weeks, I started getting the message bellow in my logs:

```auto
[2017-12-27T20:33:49,547][WARN][logstash.outputs.elasticsearch] Could not index event to Elasticsearch. {:status=>400, :action=>["index", {:_id=>nil, :_index=>"netflow-2017.12.27", :_type=>"doc", :_routing=>nil}, #<LogStash::Event:0x781a020d>], :response=>{"index"=>{"_index"=>"netflow-2017.12.27", "_type"=>"doc", "_id"=>"zlaumWABILE779PdXcPq", "status"=>400, "error"=>{"type"=>"mapper_parsing_exception", "reason"=>"failed to parse [netflow.conn_id]", "caused_by"=>{"type"=>"json_parse_exception", "reason"=>"Numeric value (2453470754) out of range of int\n at [Source: org.elasticsearch.common.bytes.BytesReference$MarkSupportingStreamInputWrapper@6d5ef212; line: 1, column: 609]"}}}}}

```

The flow information Logstash is processing is coming from a Cisco ASA.

I tried editing the `netwflow.json` under `logstash-6.1.1/modules/netflow/configuration/elasticsearch` and running logstash with `setup` again, and I could confirm that Elasticsearch template was updated with `curl localhost:9200/_template/netflow`, but after restarting Elasticsearch and logstash the issue persisted.

Any ideas?

Thanks!

---

<div class="post-metadata">

**Author:** ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)\
**Post date:** [December 31, 2017, 1:23pm UTC](https://discuss.elastic.co/t/netflow-conn-id-out-of-range/113363/2 "2017-12-31T13:23:45Z")

</div>

You'll have to use an index template to force the netflow.conn\_id field as a long, then reindex the data to a new index where said field actually is a long field.

---

<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 28, 2018, 1:35pm UTC](https://discuss.elastic.co/t/netflow-conn-id-out-of-range/113363/3 "2018-01-28T13:35:09Z")

</div>

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