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!

Agentic SOC Triage: Investigating Splunk ES Notables with MCP Server and a Local LLM

The Problem: Too Many Alerts, Too Little Context Security operations teams running Splunk Enterprise Security ...

All Work and No Play? Not at .conf26! Unwind at These Evening Events

Between hands-on technical sessions, keynote reveals, and diving into live architectures, .conf26 is packed ...

Join the Hackathon at .conf26 and build a No-Code AI agent

Join us for the AI Agent Buildathon, an in-person, three-hour hands-on Hackathon where you’ll use Splunk Agent ...