# Packetbeat local usage without elastic search

**URL:** <https://discuss.elastic.co/t/packetbeat-local-usage-without-elastic-search/141981>\
**Category:** Beats\
**Created:** [July 27, 2018, 6:12pm UTC](https://discuss.elastic.co/t/packetbeat-local-usage-without-elastic-search/141981 "2018-07-27T18:12:01Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![acsarnaik](https://avatars.discourse-cdn.com/v4/letter/a/f17d59/32.png) [@acsarnaik](https://discuss.elastic.co/u/acsarnaik)\
**Post date:** [July 27, 2018, 6:12pm UTC](https://discuss.elastic.co/t/packetbeat-local-usage-without-elastic-search/141981/1 "2018-07-27T18:12:01Z")

</div>

Can packetbeat support local reporting of packets that are captured for a particular protocol, such as DNS, DHCP? Or does it have APIs to get the packet information such as DNS options without installing elasticsearch and kibana. Looking for off-the-shelf protocol specific packet capture and either notification or API interface to get the information.

---

<div class="post-metadata">

**Author:** ![shaunak](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/shaunak/32/6643_2.png) [@shaunak](https://discuss.elastic.co/u/shaunak)\
**Post date:** [July 27, 2018, 6:21pm UTC](https://discuss.elastic.co/t/packetbeat-local-usage-without-elastic-search/141981/2 "2018-07-27T18:21:38Z")

</div>

Packetbeat supports outputs other than `elasticsearch`. For your use case perhaps you could use the `kafka` output and then consume from Kafka? Or use the `logstash` output and then configure [Logstash](https://www.elastic.co/guide/en/logstash/current/getting-started-with-logstash.html) to send the information to further destinations. I'm not sure exactly what you mean by "notification" but Logstash has a generic [`http` output](https://www.elastic.co/guide/en/logstash/current/plugins-outputs-http.html) to send data to an arbitrary HTTP endpoint (i.e. a web hook).

---

<div class="post-metadata">

**Author:** ![acsarnaik](https://avatars.discourse-cdn.com/v4/letter/a/f17d59/32.png) [@acsarnaik](https://discuss.elastic.co/u/acsarnaik)\
**Post date:** [July 27, 2018, 8:30pm UTC](https://discuss.elastic.co/t/packetbeat-local-usage-without-elastic-search/141981/3 "2018-07-27T20:30:45Z")

</div>

Hello Shaunak,

Thanks for responding. I would have liked to have packetbeat send the http post with the packet content to our end point.

Regards,

---

<div class="post-metadata">

**Author:** ![acsarnaik](https://avatars.discourse-cdn.com/v4/letter/a/f17d59/32.png) [@acsarnaik](https://discuss.elastic.co/u/acsarnaik)\
**Post date:** [August 7, 2018, 10:17pm UTC](https://discuss.elastic.co/t/packetbeat-local-usage-without-elastic-search/141981/4 "2018-08-07T22:17:52Z")

</div>

Hello Shaunak,

Have not heard from you. As I mentioned in my previous reply, can packetbeat packet data to an HTTP endpoint directly rather than Logstash doing that please.

Regards,

Ajit

---

<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:** [September 5, 2018, 12:18am UTC](https://discuss.elastic.co/t/packetbeat-local-usage-without-elastic-search/141981/5 "2018-09-05T00:18:08Z")

</div>

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