# Access connection data using flow Id

**URL:** <https://discuss.elastic.co/t/access-connection-data-using-flow-id/162507>\
**Category:** Beats\
**Tags:** packetbeat\
**Created:** [December 31, 2018, 10:56am UTC](https://discuss.elastic.co/t/access-connection-data-using-flow-id/162507 "2018-12-31T10:56:29Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![adrisr](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/adrisr/32/25423_2.png) [@adrisr](https://discuss.elastic.co/u/adrisr)\
**Post date:** [January 2, 2019, 3:47pm UTC](https://discuss.elastic.co/t/access-connection-data-using-flow-id/162507/2 "2019-01-02T15:47:46Z")

</div>

Hi, currently this is not possible as flows and protos are separated and flow analysis only looks at packet headers and not to TCP payload.

The `tls` protocol in Packetbeat doesn't have all the information you need?

---

_[View the full topic](https://discuss.elastic.co/t/access-connection-data-using-flow-id/162507)._