# View full stack trace in Discover search

**URL:** <https://discuss.elastic.co/t/view-full-stack-trace-in-discover-search/171157>\
**Category:** Kibana\
**Created:** [March 6, 2019, 5:03pm UTC](https://discuss.elastic.co/t/view-full-stack-trace-in-discover-search/171157 "2019-03-06T17:03:44Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![MSkiLLz](https://avatars.discourse-cdn.com/v4/letter/m/41988e/32.png) [@MSkiLLz](https://discuss.elastic.co/u/MSkiLLz)\
**Post date:** [March 6, 2019, 5:03pm UTC](https://discuss.elastic.co/t/view-full-stack-trace-in-discover-search/171157/1 "2019-03-06T17:03:44Z")

</div>

Hello,

I'm a first time Kibana user. Currently I am able to view the log details of my application within Kibana but the entire stack trace does not show within one message. The stack trace is being split line by line within several Time/messages. What type of modification can I make to view the full stack trace in one message?

---

<div class="post-metadata">

**Author:** ![xeraa](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/xeraa/32/48181_2.png) [@xeraa](https://discuss.elastic.co/u/xeraa)\
**Post date:** [March 6, 2019, 10:27pm UTC](https://discuss.elastic.co/t/view-full-stack-trace-in-discover-search/171157/2 "2019-03-06T22:27:00Z")

</div>

Once a multiline message is broken up, putting it back together in the right order is rather complicated. You should avoid breaking it up in the first place, for example with the [multiline features in Filebeat](https://www.elastic.co/guide/en/beats/filebeat/current/multiline-examples.html).

---

<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:** [April 3, 2019, 10:27pm UTC](https://discuss.elastic.co/t/view-full-stack-trace-in-discover-search/171157/3 "2019-04-03T22:27:05Z")

</div>

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