Getting Data In

Character encoding when sending to TCP port

helge
Builder

I am sending data to a TCP port I configured for input on the Splunk server. How should the (string) data be encoded - ASCII, ANSI (in that case: which codepage?), UTF-8 or UTF-16 (aka UCS-2)?

0 Karma
1 Solution

helge
Builder

Based on my experiments it seems Splunk expects the encoding to be UTF-8. I sent strings with German, Greek and Russing special characters and they were displayed correctly in the web UI.

Example:

alt text

I also tried UCS-2, but that did not work out too well:

alt text

View solution in original post

0 Karma

helge
Builder

Based on my experiments it seems Splunk expects the encoding to be UTF-8. I sent strings with German, Greek and Russing special characters and they were displayed correctly in the web UI.

Example:

alt text

I also tried UCS-2, but that did not work out too well:

alt text

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!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...