Getting Data In

German umaulat Character is not getting recognized by Splunk Universal Forwarder

naiktej13
Engager

My PowerShell script results with "german umaulat" character into data. In our local lab Splunk Universal Forwarder runs this script at some interval and forwards data to Splunk Enterprise(SearchHead)

Now when I manually run this script, I can see that character without encoding(original value ) but when I receive the events from UF, I can see that those characters are encoded on my SH.I have also added "CHARSET=UTF-8" into props.conf on both side(forwarder and receiver)

Now my questions are:
1) Does Universal Forwarder read props.conf?
2) Where should I handle this characters?

Tags (2)
0 Karma

jkat54
SplunkTrust
SplunkTrust
  1. Yes, UF reads props on some occasions such as everything under "Structured Data Header Extraction and configuration" in props.conf.spec and everywhere else you see "this setting is for forwarders" (Just search the page for "forwarder", you'll see them)

  2. Character Encoding happens in the Parsing Queue which happens on heavy forwarders and indexers

http://docs.splunk.com/Documentation/Splunk/latest/Deploy/Datapipeline
http://docs.splunk.com/Documentation/Splunk/6.5.1/Deploy/Componentsofadistributedenvironment

To solve your encoding problem, try setting the CHARSET=iso-8859-1 instead.

0 Karma
Get Updates on the Splunk Community!

What's new in Splunk Cloud Platform 9.1.2312?

Hi Splunky people! We are excited to share the newest updates in Splunk Cloud Platform 9.1.2312! Analysts can ...

What’s New in Splunk Security Essentials 3.8.0?

Splunk Security Essentials (SSE) is an app that can amplify the power of your existing Splunk Cloud Platform, ...

Let’s Get You Certified – Vegas-Style at .conf24

Are you ready to level up your Splunk game? Then, let’s get you certified live at .conf24 – our annual user ...