Getting Data In

encoded data over tcp

shangshin
Builder

Hi I am able to send log4j log data to splunk over tcp network but the data in splunk is not human readable.(see below) This is totally different than the original log data. Can anyone shed some light on this? Thanks!

log4j.properties
log4j.rootCategory=INFO, socket
log4j.appender.socket=org.apache.log4j.net.SocketAppender
log4j.appender.socket.port=33333
log4j.appender.socket.remoteHost=myLinuxServer1

tcp:33333

\xAC\xED\x00\x5sr\x00!org.apache.log4j.spi.LoggingEvent\xF3\xF2\xB9#t\xB\xB5?\x3\x00
Z\x00\x15mdcCopyLookupRequiredZ\x00\x11ndcLookupRequiredJ\x00   timeStampL\x00\xCcategoryNamet\x00\x12Ljava/lang/String;L\x00\xClocationInfot\x00#Lorg/apache/log4j/spi/LocationInfo;L\x00\x7mdcCopyt\x00\x15Ljava/util/Hashtable;L\x00\x3ndcq\x00~\x00\x1L\x00\xFrenderedMessageq\x00~\x00\x1L\x00
Tags (3)

helge
Builder

I can only guess that the character encoding is not UTF-8. See this answer for more information.

0 Karma
Get Updates on the Splunk Community!

Building Reliable Asset and Identity Frameworks in Splunk ES

 Accurate asset and identity resolution is the backbone of security operations. Without it, alerts are ...

Cloud Monitoring Console - Unlocking Greater Visibility in SVC Usage Reporting

For Splunk Cloud customers, understanding and optimizing Splunk Virtual Compute (SVC) usage and resource ...

Automatic Discovery Part 3: Practical Use Cases

If you’ve enabled Automatic Discovery in your install of the Splunk Distribution of the OpenTelemetry ...