# Feature Request Flowbeat!

**URL:** <https://discuss.elastic.co/t/feature-request-flowbeat/1957>\
**Category:** Beats\
**Tags:** packetbeat\
**Created:** [June 4, 2015, 6:25pm UTC](https://discuss.elastic.co/t/feature-request-flowbeat/1957 "2015-06-04T18:25:15Z")\
**Posts on this page:** 13\
**Page:** 1

<div class="post-metadata">

**Author:** ![Steve\_Kelley](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/steve_kelley/32/522_2.png) [@Steve\_Kelley](https://discuss.elastic.co/u/Steve_Kelley)\
**Post date:** [June 4, 2015, 6:25pm UTC](https://discuss.elastic.co/t/feature-request-flowbeat/1957/1 "2015-06-04T18:25:15Z")

</div>

Love the packet beat analyzer! Is there future plans for analyzing flows? IE: S-Flow, Netflow?

---

<div class="post-metadata">

**Author:** ![tudor](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tudor/32/3753_2.png) [@tudor](https://discuss.elastic.co/u/tudor)\
**Post date:** [June 8, 2015, 2:59pm UTC](https://discuss.elastic.co/t/feature-request-flowbeat/1957/2 "2015-06-08T14:59:29Z")

</div>

Yes, a beat for flows (flowbeat or something) would make sense to me.

---

<div class="post-metadata">

**Author:** ![andsch](https://avatars.discourse-cdn.com/v4/letter/a/ad7895/32.png) [@andsch](https://discuss.elastic.co/u/andsch)\
**Post date:** [June 15, 2015, 9:27pm UTC](https://discuss.elastic.co/t/feature-request-flowbeat/1957/3 "2015-06-15T21:27:57Z")

</div>

+1  
and IPFIX 🙂

---

<div class="post-metadata">

**Author:** ![tbragin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tbragin/32/45166_2.png) [@tbragin](https://discuss.elastic.co/u/tbragin)\
**Post date:** [June 17, 2015, 12:28am UTC](https://discuss.elastic.co/t/feature-request-flowbeat/1957/4 "2015-06-17T00:28:56Z")

</div>

For now, there is also a way to get Netflow data into Elasticsearch via Logstash using the UDP input and a Netflow codec:  
[https://www.elastic.co/guide/en/logstash/current/plugins-codecs-netflow.html](https://www.elastic.co/guide/en/logstash/current/plugins-codecs-netflow.html)  
[http://blogs.cisco.com/security/step-by-step-setup-of-elk-for-netflow-analytics](http://blogs.cisco.com/security/step-by-step-setup-of-elk-for-netflow-analytics)

---

<div class="post-metadata">

**Author:** ![Paul\_MONSON](https://avatars.discourse-cdn.com/v4/letter/p/9fc29f/32.png) [@Paul\_MONSON](https://discuss.elastic.co/u/Paul_MONSON)\
**Post date:** [September 23, 2015, 9:45pm UTC](https://discuss.elastic.co/t/feature-request-flowbeat/1957/5 "2015-09-23T21:45:34Z")

</div>

+1  
This would be great

---

<div class="post-metadata">

**Author:** ![rharrisssi](https://avatars.discourse-cdn.com/v4/letter/r/f07891/32.png) [@rharrisssi](https://discuss.elastic.co/u/rharrisssi)\
**Post date:** [October 21, 2015, 8:44pm UTC](https://discuss.elastic.co/t/feature-request-flowbeat/1957/6 "2015-10-21T20:44:01Z")

</div>

+1  
I would like to see this feature.

---

<div class="post-metadata">

**Author:** ![german23](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/german23/32/11052_2.png) [@german23](https://discuss.elastic.co/u/german23)\
**Post date:** [October 23, 2015, 6:47am UTC](https://discuss.elastic.co/t/feature-request-flowbeat/1957/7 "2015-10-23T06:47:18Z")

</div>

+1  
Something like [http://www.pmacct.net/](http://www.pmacct.net/) with direct elasticsearch integration would be great!

---

<div class="post-metadata">

**Author:** ![FStelzer](https://avatars.discourse-cdn.com/v4/letter/f/f14d63/32.png) [@FStelzer](https://discuss.elastic.co/u/FStelzer)\
**Post date:** [February 17, 2016, 3:12pm UTC](https://discuss.elastic.co/t/feature-request-flowbeat/1957/8 "2016-02-17T15:12:57Z")

</div>

Take a look at: [https://github.com/FStelzer/flowbeat](https://github.com/FStelzer/flowbeat)  
It's still a prototype and not all available sflow data is parsed yet but for collecting network metrics from my brocade routers it works rather well.  
Feel free to add parsers to the underlying sflow lib 🙂

Please be aware that the exported data format will change! Currently it shoves the on-wire data structure directly into elasticsearch which makes metrics on certain fields rather hard.

---

<div class="post-metadata">

**Author:** ![tudor](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tudor/32/3753_2.png) [@tudor](https://discuss.elastic.co/u/tudor)\
**Post date:** [February 19, 2016, 6:33pm UTC](https://discuss.elastic.co/t/feature-request-flowbeat/1957/9 "2016-02-19T18:33:41Z")

</div>

Cool, @FStelzer! You might want to open a pull request to add it [https://github.com/elastic/beats/blob/master/libbeat/docs/communitybeats.asciidoc](https://github.com/elastic/beats/blob/master/libbeat/docs/communitybeats.asciidoc)

I can also add it for you if you prefer.

---

<div class="post-metadata">

**Author:** ![kiphat](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kiphat/32/57020_2.png) [@kiphat](https://discuss.elastic.co/u/kiphat)\
**Post date:** [March 17, 2016, 6:21pm UTC](https://discuss.elastic.co/t/feature-request-flowbeat/1957/10 "2016-03-17T18:21:09Z")

</div>

I know it's an old thread... I've been using PMACCT for SFlow and NetFlow capture. It has a module to integrate with RabbitMQ. Logstash pulls from RabbitMQ and forwards on to Elastic. The fields are setup by PMACCT so the whole transaction is pretty simple and straight-forward. [http://www.pmacct.net/](http://www.pmacct.net/)

---

<div class="post-metadata">

**Author:** ![Jeremy\_Foran](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jeremy_foran/32/15434_2.png) [@Jeremy\_Foran](https://discuss.elastic.co/u/Jeremy_Foran)\
**Post date:** [June 27, 2017, 7:10pm UTC](https://discuss.elastic.co/t/feature-request-flowbeat/1957/11 "2017-06-27T19:10:43Z")

</div>

Good luck, have you tried using it? Almost ever posting about it is the exact same:

[2017-06-27T18:50:42,504][WARN][logstash.codecs.netflow] No matching template for flow id 34237

---

<div class="post-metadata">

**Author:** ![nana123](https://avatars.discourse-cdn.com/v4/letter/n/2bfe46/32.png) [@nana123](https://discuss.elastic.co/u/nana123)\
**Post date:** [June 28, 2017, 5:30am UTC](https://discuss.elastic.co/t/feature-request-flowbeat/1957/13 "2017-06-28T05:30:01Z")

</div>

The suggestions for this information are very interesting.

---

<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:** [November 4, 2022, 4:00am UTC](https://discuss.elastic.co/t/feature-request-flowbeat/1957/15 "2022-11-04T04:00:42Z")

</div>


