# Netflow module on ELK 6.1.2

**URL:** <https://discuss.elastic.co/t/netflow-module-on-elk-6-1-2/116980>\
**Category:** Logstash\
**Created:** [January 25, 2018, 6:55am UTC](https://discuss.elastic.co/t/netflow-module-on-elk-6-1-2/116980 "2018-01-25T06:55:41Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![kencrozier](https://avatars.discourse-cdn.com/v4/letter/k/ba9def/32.png) [@kencrozier](https://discuss.elastic.co/u/kencrozier)\
**Post date:** [January 25, 2018, 6:55am UTC](https://discuss.elastic.co/t/netflow-module-on-elk-6-1-2/116980/1 "2018-01-25T06:55:41Z")

</div>

I have Netflow v9 coming in from a Fortinet firewall and can see a list of the native flows in the dashboards, but they all have this warning

\_\_netflow\_ip\_version\_not\_recognized, \_\_netflow\_direction\_not\_recognized

however nothing else is showing and i'm getting this message in the logstash log

[logstash.outputs.elasticsearch] Could not index event to Elasticsearch. {:status=\>400, :action=\>["index", {:\_id=\>nil, :\_index=\>"netflow-2018.01.25", :\_type=\>"doc", :\_routing=\>nil}, #LogStash::Event:0x6a4e2625], :response=\>{"index"=\>{"\_index"=\>"netflow-2018.01.25", "\_type"=\>"doc", "\_id"=\>"6DcOLGEBR5Jkz-52CTIu", "status"=\>400, "error"=\>{"type"=\>"mapper\_parsing\_exception", "reason"=\>"failed to parse [netflow.application\_id]", "caused\_by"=\>{"type"=\>"number\_format\_exception", "reason"=\>"For input string: "20:53068615909376""}}}}}

what is going wrong, is this a known problem ???? I thought that the netflow module was plug and play ... not totally impressed so far ...

---

<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 22, 2018, 6:56am UTC](https://discuss.elastic.co/t/netflow-module-on-elk-6-1-2/116980/2 "2018-02-22T06:56:18Z")

</div>

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