# Catched library exception still marked as Exception in APM UI

**URL:** <https://discuss.elastic.co/t/catched-library-exception-still-marked-as-exception-in-apm-ui/337201>\
**Category:** APM\
**Tags:** java\
**Created:** [June 29, 2023, 1:20pm UTC](https://discuss.elastic.co/t/catched-library-exception-still-marked-as-exception-in-apm-ui/337201 "2023-06-29T13:20:43Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Jack\_Shirazi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jack_shirazi/32/91641_2.png) [@Jack\_Shirazi](https://discuss.elastic.co/u/Jack_Shirazi)\
**Post date:** [July 13, 2023, 1:58pm UTC](https://discuss.elastic.co/t/catched-library-exception-still-marked-as-exception-in-apm-ui/337201/2 "2023-07-13T13:58:40Z")

</div>

My colleague Sylvain has a [nice explanation](https://discuss.elastic.co/t/not-all-errors-exceptions-are-reported-by-the-java-apm-agent/260157/2). I think you would need to [exclude](https://www.elastic.co/guide/en/apm/agent/java/current/config-core.html#config-disable-instrumentations) `process` from the instrumentation to avoid this one

---

_[View the full topic](https://discuss.elastic.co/t/catched-library-exception-still-marked-as-exception-in-apm-ui/337201)._