Splunk Dev

EventViewer results for java stack trace gets cut off

gtesser
New Member

java exceptions from log4j are not showing the whole stack trace on the search results. Some of them are but others dont. Have already increased the max lines to 1000 but still nothing. Any idea?

Tags (1)
0 Karma

lguinn2
Legend

Maybe Splunk is not accurately breaking the lines? Run a search and look for an event that has been truncated. Then choose "Show Source" from the pull-down arrow to the left of the event. When you see the event in context, do the following lines appear? If yes, but they are not highlighted, then you have a line-breaking problem.
Look here for help on linebreaking.

0 Karma
Get Updates on the Splunk Community!

Technical Workshop Series: Splunk Data Management and SPL2 | Register here!

Hey, Splunk Community! Ready to take your data management skills to the next level? Join us for a 3-part ...

Spotting Financial Fraud in the Haystack: A Guide to Behavioral Analytics with Splunk

In today's digital financial ecosystem, security teams face an unprecedented challenge. The sheer volume of ...

Solve Problems Faster with New, Smarter AI and Integrations in Splunk Observability

Solve Problems Faster with New, Smarter AI and Integrations in Splunk Observability As businesses scale ...