Solved: Character encoding when sending to TCP port

helge · ‎03-31-2014

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)?

helge · ‎03-31-2014

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:

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

View solution in original post

helge · ‎03-31-2014

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:

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

Character encoding when sending to TCP port

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

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

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

Build resilience for the agentic era: Join us at Splunk Go San Jose

Manage Edge Processor pipelines end to end with APIs

Join the Conversation