# URL shortening services monitoring via ELK

**URL:** https://discuss.elastic.co/t/url-shortening-services-monitoring-via-elk/341911
**Category:** Elastic Security
**Created:** [August 29, 2023, 4:05pm UTC](https://discuss.elastic.co/t/url-shortening-services-monitoring-via-elk/341911 "2023-08-29T16:05:42Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![Ragul\_venkatasubban](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ragul_venkatasubban/32/125074_2.png) [@Ragul\_venkatasubban](https://discuss.elastic.co/u/Ragul_venkatasubban)
#### Post date: [August 29, 2023, 4:05pm UTC](https://discuss.elastic.co/t/url-shortening-services-monitoring-via-elk/341911/1 "2023-08-29T16:05:42Z")

</div>

Hey,

I have integrated firewall logs in ELK. I came across some logs which are of URL shorteners eg., bit[.]ly, etc.. the interesting part is when a user clicks on these kinds of URLs we won't know the original URL and we won't have visibility unless and until the user does something on that final URL.

If someone has a solution or a workaround to tackle these kinds of situations please let me know.

Thanks in advance 🙂

---

<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 26, 2023, 4:06pm UTC](https://discuss.elastic.co/t/url-shortening-services-monitoring-via-elk/341911/2 "2023-09-26T16:06:08Z")

</div>

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