# "url.full" field not viewing in Packetbeat 7.16.3

**URL:** <https://discuss.elastic.co/t/url-full-field-not-viewing-in-packetbeat-7-16-3/294954>\
**Category:** Beats\
**Tags:** packetbeat\
**Created:** [January 20, 2022, 1:42pm UTC](https://discuss.elastic.co/t/url-full-field-not-viewing-in-packetbeat-7-16-3/294954 "2022-01-20T13:42:02Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![ethical20](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ethical20/32/68123_2.png) [@ethical20](https://discuss.elastic.co/u/ethical20)\
**Post date:** [January 21, 2022, 7:46am UTC](https://discuss.elastic.co/t/url-full-field-not-viewing-in-packetbeat-7-16-3/294954/3 "2022-01-21T07:46:48Z")

</div>

Thanks for your reply @legoguy1000

I've tested both, even [google.com](https://discuss.elastic.co/t/hadoop-getting-elasticsearch-hadoop-working-with-shark/15882) is not logging. In all ways the config file should be grabbing both _http_ and _https_.

---

_[View the full topic](https://discuss.elastic.co/t/url-full-field-not-viewing-in-packetbeat-7-16-3/294954)._