# Monitoring HTTPS

**URL:** <https://discuss.elastic.co/t/monitoring-https/87940>\
**Category:** Beats\
**Tags:** packetbeat\
**Created:** [June 1, 2017, 3:33pm UTC](https://discuss.elastic.co/t/monitoring-https/87940 "2017-06-01T15:33:25Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Gilberto](https://avatars.discourse-cdn.com/v4/letter/g/958977/32.png) [@Gilberto](https://discuss.elastic.co/u/Gilberto)\
**Post date:** [June 1, 2017, 3:33pm UTC](https://discuss.elastic.co/t/monitoring-https/87940/1 "2017-06-01T15:33:25Z")

</div>

How can I monitoring Https with packetbeat?

---

<div class="post-metadata">

**Author:** ![andrewkroh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andrewkroh/32/3784_2.png) [@andrewkroh](https://discuss.elastic.co/u/andrewkroh)\
**Post date:** [June 2, 2017, 1:42am UTC](https://discuss.elastic.co/t/monitoring-https/87940/2 "2017-06-02T01:42:20Z")

</div>

You can't really monitor the application layer contents of a TLS encrypted connection. Packetbeat can report [flow data](https://www.elastic.co/guide/en/beats/packetbeat/current/flows.html) for the connections but it won't be able to "see" inside to get the HTTP details.

You can do monitoring if you employ some sort of SSL offloading and setup Packetbeat to look at the unencrypted traffic.

---

<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:** [June 22, 2017, 3:33pm UTC](https://discuss.elastic.co/t/monitoring-https/87940/3 "2017-06-22T15:33:29Z")

</div>

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