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
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Accelerate Splunk App Development with AI

  Learn how to automate the repetitive parts of your build cycle.   Watch On-Demand   Replay the Accelerate ...

Splunk Agent Observability: Measuring AI Value with Splunk Tokenomics on AWS

The AI landscape is moving faster than ever, and our latest 2026 State of Observability report provides the ...

Enterprise Security Watch Party: What’s New in 8.8 - Recap

Splunk Community HQ hosted a Splunk Enterprise Security Watch Party: What’s New In ES 8.8 last Thursday. I had ...