# Capturing Traffic over websockets

**URL:** <https://discuss.elastic.co/t/capturing-traffic-over-websockets/78940>\
**Category:** Beats\
**Tags:** packetbeat\
**Created:** [March 16, 2017, 10:37pm UTC](https://discuss.elastic.co/t/capturing-traffic-over-websockets/78940 "2017-03-16T22:37:37Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![jnmoore](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jnmoore/32/16440_2.png) [@jnmoore](https://discuss.elastic.co/u/jnmoore)\
**Post date:** [March 16, 2017, 10:37pm UTC](https://discuss.elastic.co/t/capturing-traffic-over-websockets/78940/1 "2017-03-16T22:37:37Z")

</div>

Can packetbeat capture websocket traffic? If so, what kind of information is it able to log?

---

<div class="post-metadata">

**Author:** ![ruflin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ruflin/32/3116_2.png) [@ruflin](https://discuss.elastic.co/u/ruflin)\
**Post date:** [March 20, 2017, 9:26am UTC](https://discuss.elastic.co/t/capturing-traffic-over-websockets/78940/2 "2017-03-20T09:26:39Z")

</div>

Websocket is currently not supported. But we are always looking for new protocols 😉 [https://www.elastic.co/guide/en/beats/packetbeat/5.2/new-protocol.html](https://www.elastic.co/guide/en/beats/packetbeat/5.2/new-protocol.html)

Feel free to also open a feature request for it on Github

---

<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:** [April 6, 2017, 10:38pm UTC](https://discuss.elastic.co/t/capturing-traffic-over-websockets/78940/3 "2017-04-06T22:38:05Z")

</div>

This topic was automatically closed after 21 days. New replies are no longer allowed.