# Adding Additional Properties in Error logs

**URL:** <https://discuss.elastic.co/t/adding-additional-properties-in-error-logs/357762>\
**Category:** Elastic Observability\
**Tags:** elastic-stack-monitoring\
**Created:** [April 19, 2024, 5:37am UTC](https://discuss.elastic.co/t/adding-additional-properties-in-error-logs/357762 "2024-04-19T05:37:50Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Arpan\_Mondal](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/arpan_mondal/32/133629_2.png) [@Arpan\_Mondal](https://discuss.elastic.co/u/Arpan_Mondal)\
**Post date:** [April 19, 2024, 5:37am UTC](https://discuss.elastic.co/t/adding-additional-properties-in-error-logs/357762/1 "2024-04-19T05:37:50Z")

</div>

Hi team,  
We are using `@elastic/apm-rum` in a Nextjs application for Real User Monitoring.  
On Deploying and checking the error logs we are seeing some unkown Error culprits(inline script) being identified as shown in the image below.

- It would be helpful if anyone from the team can throw some light on what is this `(inline script)`.
- One more question, how can we pass `additional properties` to be shown in this error block, so that its easier to debug source of logs, such as request urls for http errors, or any method name causing the errors.

Thank you

 ![elastic_community_question](https://us1.discourse-cdn.com/elastic/original/3X/7/d/7d21df45eecc3418eb7d6b30814d7e14d586dbfc.png)