Getting Data In

Is the CHARSET setting also available for Hunk in props.conf?

eichfuss
Path Finder

Is the CHARSET Setting also available for Hunk in the props.conf?

Thanks, Regards
Sven

Tags (3)
0 Karma

Ledion_Bitincka
Splunk Employee
Splunk Employee

Yes it is. Are you seeing something different or experiencing any issues?

0 Karma

Ledion_Bitincka
Splunk Employee
Splunk Employee

Hmm, that's strange, does any of the following configs actually get the charset set right? Basically trying to see if there's either another source:: stanza that matches and sets the CHARSET (due to wildcarding) or an automatic sourcetype that overrides your setting

[source::/data/com_data_log*/...]
TIME_PREFIX="created":
SHOULD_LINEMERGE=false
NO_BINARY_CHECK=true
CHARSET = Latin-1
# setting priority should ensure that the settings of this stanza are layered on *top* of other matches 
priority = 100

How about the following?

[source::/data/com_data_log*/...]
TIME_PREFIX="created":
SHOULD_LINEMERGE=false
NO_BINARY_CHECK=true
sourcetype = my-sourcetype
priority = 100

[my-sourcetype]
CHARSET=Latin-1
0 Karma

eichfuss
Path Finder

Yes, I tried to use the CHARSET = latin-1 setting, but it dosen't work. I put this in the props.conf under /system/local on the hunk Server.

props.conf
[source::/data/com_data_log*/...]
TIME_PREFIX="created":
SHOULD_LINEMERGE=false
NO_BINARY_CHECK=true
CHARSET=Latin-1

0 Karma
.conf21 CFS Extended through 5/20!

Don't miss your chance
to share your Splunk
wisdom in-person or
virtually at .conf21!

Call for Speakers has
been extended through
Thursday, 5/20!