# Is there solution for collect frontend log

**URL:** <https://discuss.elastic.co/t/is-there-solution-for-collect-frontend-log/321024>\
**Category:** Elastic Observability\
**Created:** [December 12, 2022, 11:32am UTC](https://discuss.elastic.co/t/is-there-solution-for-collect-frontend-log/321024 "2022-12-12T11:32:36Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![Allen\_Wei](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/allen_wei/32/98900_2.png) [@Allen\_Wei](https://discuss.elastic.co/u/Allen_Wei)\
**Post date:** [December 12, 2022, 11:32am UTC](https://discuss.elastic.co/t/is-there-solution-for-collect-frontend-log/321024/1 "2022-12-12T11:32:36Z")

</div>

Is there solution send frontend log from browser to Elastic? The only thing I found is fleet custom http server.

---

<div class="post-metadata">

**Author:** ![Kevin\_Delemme](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kevin_delemme/32/108920_2.png) [@Kevin\_Delemme](https://discuss.elastic.co/u/Kevin_Delemme)\
**Post date:** [December 12, 2022, 1:34pm UTC](https://discuss.elastic.co/t/is-there-solution-for-collect-frontend-log/321024/2 "2022-12-12T13:34:45Z")

</div>

Hey @Allen_Wei,

Have you looked into RUM [Real User Monitoring (RUM) | APM User Guide [8.5] | Elastic](https://www.elastic.co/guide/en/apm/guide/current/apm-rum.html) yet?

---

<div class="post-metadata">

**Author:** ![Allen\_Wei](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/allen_wei/32/98900_2.png) [@Allen\_Wei](https://discuss.elastic.co/u/Allen_Wei)\
**Post date:** [December 13, 2022, 3:04am UTC](https://discuss.elastic.co/t/is-there-solution-for-collect-frontend-log/321024/3 "2022-12-13T03:04:45Z")

</div>

Yes, I checked RUM, but what I need is collect event log from frontend

---

<div class="post-metadata">

**Author:** ![coenwarmer](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/coenwarmer/32/110063_2.png) [@coenwarmer](https://discuss.elastic.co/u/coenwarmer)\
**Post date:** [December 13, 2022, 9:25am UTC](https://discuss.elastic.co/t/is-there-solution-for-collect-frontend-log/321024/4 "2022-12-13T09:25:54Z")

</div>

Hey @Allen_Wei, what sort of frontend events are you looking to track?

---

<div class="post-metadata">

**Author:** ![Allen\_Wei](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/allen_wei/32/98900_2.png) [@Allen\_Wei](https://discuss.elastic.co/u/Allen_Wei)\
**Post date:** [December 13, 2022, 9:49am UTC](https://discuss.elastic.co/t/is-there-solution-for-collect-frontend-log/321024/5 "2022-12-13T09:49:03Z")

</div>

For example

1. User behavior event tracking,
2. Frontend debug logs

---

<div class="post-metadata">

**Author:** ![Alberto\_Delgado](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alberto_delgado/32/98488_2.png) [@Alberto\_Delgado](https://discuss.elastic.co/u/Alberto_Delgado)\
**Post date:** [December 14, 2022, 9:43am UTC](https://discuss.elastic.co/t/is-there-solution-for-collect-frontend-log/321024/6 "2022-12-14T09:43:58Z")

</div>

Hi @Allen_Wei,

Thanks for reaching out!

Do you mean to have the possibility of sending custom logs on demand? If you mean that, unfortunately, we don't have that feature at the moment. The "closest" things that we have are:

- [custom transactions](https://www.elastic.co/guide/en/apm/agent/rum-js/master/custom-transactions.html). (in case you want to log/measure certain flows)
- [global labels](https://www.elastic.co/guide/en/apm/agent/rum-js/5.x/agent-api.html#apm-add-labels) and [transaction labels](https://www.elastic.co/guide/en/apm/agent/rum-js/5.x/transaction-api.html#transaction-add-labels)

But as you can see that is not the same due to the fact that at the end of the day everything ends linked to a transaction/error. As mentioned above, we cannot send logs as an "independent entity" at the moment.

Btw, when it comes to `User behavior event tracking` the agent intercepts user clicks to create transactions. More info [here](https://www.elastic.co/guide/en/apm/agent/rum-js/5.x/intro.html#features) and [here](https://www.elastic.co/guide/en/apm/agent/rum-js/5.x/supported-technologies.html#user-interactions)

Let me know if this helps you.

Thanks,  
Alberto

---

<div class="post-metadata">

**Author:** ![Allen\_Wei](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/allen_wei/32/98900_2.png) [@Allen\_Wei](https://discuss.elastic.co/u/Allen_Wei)\
**Post date:** [December 16, 2022, 8:09am UTC](https://discuss.elastic.co/t/is-there-solution-for-collect-frontend-log/321024/7 "2022-12-16T08:09:30Z")

</div>

Hi @Alberto_Delgado ,

The document is very helpful. add span to transaction is definitely help.

Instead of add span to the transaction, we'd like use it as log.

1. We don't want to add those event to transaction
2. Span API does not accept more customized data.

This is more like [JavaScript Logging](https://documentation.solarwinds.com/en/success_center/loggly/content/admin/javascript.htm?cshid=loggly_javascript)

---

<div class="post-metadata">

**Author:** ![vicente.baixauli](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vicente.baixauli/32/136233_2.png) [@vicente.baixauli](https://discuss.elastic.co/u/vicente.baixauli)\
**Post date:** [July 23, 2024, 10:43am UTC](https://discuss.elastic.co/t/is-there-solution-for-collect-frontend-log/321024/8 "2024-07-23T10:43:29Z")

</div>

Is there any update regarding this "feature"?

---

<div class="post-metadata">

**Author:** ![Patryk\_Pomykalski](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/patryk_pomykalski/32/138968_2.png) [@Patryk\_Pomykalski](https://discuss.elastic.co/u/Patryk_Pomykalski)\
**Post date:** [November 5, 2024, 2:30pm UTC](https://discuss.elastic.co/t/is-there-solution-for-collect-frontend-log/321024/9 "2024-11-05T14:30:48Z")

</div>

any update?
