Getting Data In

json sourcetype

amanteja
Path Finder

We are logging json formatted data in our logfiles that are fed into splunk, While sending the data we use sourcetype=log4j.

Splunk is able to correctly infer the messages and shows them in the UI as json events that are clickable. However, some records despite being fully qualified json appear as text. These events show up in the UI as clear text and many Json messages are contained in that event. Why does this happen? How can we avoid this?

Tags (3)
0 Karma
1 Solution

amanteja
Path Finder

I figured that this was because the server was truncating the log event. I changed the truncate value in etc/system/local/props.conf and it solved the problem.

View solution in original post

0 Karma

amanteja
Path Finder

I figured that this was because the server was truncating the log event. I changed the truncate value in etc/system/local/props.conf and it solved the problem.

0 Karma

chaker
Contributor

You may need to post an example of the event that extracts correctly, and the one that does not.

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!

Free Professional Services for .conf26 Attendees

This year at .conf26, we are doing something a little different. We are bringing the best minds from ...

Defend at Machine Speed: Your Guide to Security Sessions at .conf26

Splunk .conf26   With threats moving at machine speed and attack surfaces expanding across hybrid ...

Where Innovation Takes Flight: The Splunk4Aviation Flight Sim Lands at .conf26

If you hear someone at .conf26 shouting "gear down, GEAR DOWN" across the show floor, you have found us.  The ...