Deployment Architecture

CHARSET does not effect when data is from a universalforwarder?

crazyeva
Contributor

Let indexer monitor a local file, CHARSET in props.conf works
But if the same file was delivered by an universalforwarder, indexer will eat it as UTF-8, nomatter what was set in indexer's props.conf!

0 Karma
1 Solution

martin_mueller
SplunkTrust
SplunkTrust

I believe that is set during the input phase on the UF, so you'll need to define the CHARSET there. http://wiki.splunk.com/Where_do_I_configure_my_Splunk_settings%3F

View solution in original post

0 Karma

martin_mueller
SplunkTrust
SplunkTrust

I believe that is set during the input phase on the UF, so you'll need to define the CHARSET there. http://wiki.splunk.com/Where_do_I_configure_my_Splunk_settings%3F

0 Karma

crazyeva
Contributor

thank you!
CHARSET -> UF's props.conf
SEDCMD,TRANSFORM -> INDEXER's props.conf
a same sourcetype stanza
solved

0 Karma
Get Updates on the Splunk Community!

.conf25 Community Recap

Hello Splunkers, And just like that, .conf25 is in the books! What an incredible few days — full of learning, ...

Splunk App Developers | .conf25 Recap & What’s Next

If you stopped by the Builder Bar at .conf25 this year, thank you! The retro tech beer garden vibes were ...

Congratulations to the 2025-2026 SplunkTrust!

Hello, Splunk Community! We are beyond thrilled to announce our newest group of SplunkTrust members!  The ...