# Send the Ruby Exception message along with the \_rubyException tag

**URL:** <https://discuss.elastic.co/t/send-the-ruby-exception-message-along-with-the-rubyexception-tag/275369>\
**Category:** Logstash\
**Created:** [June 9, 2021, 4:40am UTC](https://discuss.elastic.co/t/send-the-ruby-exception-message-along-with-the-rubyexception-tag/275369 "2021-06-09T04:40:25Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![mastersmit](https://avatars.discourse-cdn.com/v4/letter/m/f475e1/32.png) [@mastersmit](https://discuss.elastic.co/u/mastersmit)\
**Post date:** [June 9, 2021, 4:40am UTC](https://discuss.elastic.co/t/send-the-ruby-exception-message-along-with-the-rubyexception-tag/275369/1 "2021-06-09T04:40:25Z")

</div>

I have `ruby` filter processing and for some inputs, I do have ruby-exceptions and they are successfully propogated to elastic search with the tag. (expected). However I do not know why this exceptions are caused i.e the stacktrace.

May I know if there is a way to send the exception message (and stack trace) to that input such that I can trace back and see what went wrong?

---

<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:** [July 7, 2021, 4:40am UTC](https://discuss.elastic.co/t/send-the-ruby-exception-message-along-with-the-rubyexception-tag/275369/2 "2021-07-07T04:40:31Z")

</div>

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