# Bro IDS with ELK stack

**URL:** <https://discuss.elastic.co/t/bro-ids-with-elk-stack/74637>\
**Category:** Logstash\
**Created:** [February 10, 2017, 10:48am UTC](https://discuss.elastic.co/t/bro-ids-with-elk-stack/74637 "2017-02-10T10:48:26Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![ruby](https://avatars.discourse-cdn.com/v4/letter/r/13edae/32.png) [@ruby](https://discuss.elastic.co/u/ruby)\
**Post date:** [February 10, 2017, 10:48am UTC](https://discuss.elastic.co/t/bro-ids-with-elk-stack/74637/1 "2017-02-10T10:48:26Z")

</div>

I have configured BRO -IDS on PC along with Filebeat Shiipper

and from another PC on which I have installed ELK stack, I need to fetch BRO IDS logs.

please help to know what to configure on ELK stack..is there any need of python script ?

---

<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:** [February 13, 2017, 10:37am UTC](https://discuss.elastic.co/t/bro-ids-with-elk-stack/74637/2 "2017-02-13T10:37:54Z")

</div>

It sounds like you want to configure Filebeat to ship the logs you're interested in to the host with Elasticsearch (and maybe Logstash).

---

<div class="post-metadata">

**Author:** ![ruby](https://avatars.discourse-cdn.com/v4/letter/r/13edae/32.png) [@ruby](https://discuss.elastic.co/u/ruby)\
**Post date:** [February 14, 2017, 4:46am UTC](https://discuss.elastic.co/t/bro-ids-with-elk-stack/74637/3 "2017-02-14T04:46:45Z")

</div>

yes, I have confiigured filebeat, but its is not shipping IDS logs to logstash

---

<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:** [February 14, 2017, 6:36am UTC](https://discuss.elastic.co/t/bro-ids-with-elk-stack/74637/4 "2017-02-14T06:36:35Z")

</div>

Then I'd look in the Filebeat log for clues about what's going on.

---

<div class="post-metadata">

**Author:** ![ruby](https://avatars.discourse-cdn.com/v4/letter/r/13edae/32.png) [@ruby](https://discuss.elastic.co/u/ruby)\
**Post date:** [February 16, 2017, 9:20am UTC](https://discuss.elastic.co/t/bro-ids-with-elk-stack/74637/5 "2017-02-16T09:20:14Z")

</div>

{:timestamp=\>"2017-02-16T14:30:11.539000+0530", :message=\>"Beats input: the pipeline is blocked, temporary refusing new connection.", :reconnect\_backoff\_sleep=\>0.5, :level=\>:warn}

This is the error encountered

---

<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:** [February 16, 2017, 9:40am UTC](https://discuss.elastic.co/t/bro-ids-with-elk-stack/74637/6 "2017-02-16T09:40:12Z")

</div>

That's the Logstash log, but okay. Why is Logstash's pipeline blocked then? There should be clues about that too.

---

<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 16, 2017, 9:40am UTC](https://discuss.elastic.co/t/bro-ids-with-elk-stack/74637/7 "2017-03-16T09:40:23Z")

</div>

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