https://community.splunk.com/t5/Splunk-Search/Why-are-some-of-the-events-garbled-with-quot-x00-quot/m-p/13336#M1219 <P>Ideally, if you are having this symptom, you should be clear about the pattern of null characters (\x00). Are they interleaved with the expected data? Do they come in small bursts (ten bytes or so)? Are there several kilobytes worth of nulls all at once?</P> Thu, 15 Jul 2010 03:20:25 GMT jrodman 2010-07-15T03:20:25Z https://community.splunk.com/t5/Splunk-Search/Why-are-some-of-the-events-garbled-with-quot-x00-quot/m-p/13333#M1216 <P>I am indexing some logs and I see some events are filled with "\x00" while some other events are indexed correctly. </P> Wed, 12 May 2010 22:29:58 GMT https://community.splunk.com/t5/Splunk-Search/Why-are-some-of-the-events-garbled-with-quot-x00-quot/m-p/13333#M1216 elusive 2010-05-12T22:29:58Z https://community.splunk.com/t5/Splunk-Search/Why-are-some-of-the-events-garbled-with-quot-x00-quot/m-p/13334#M1217 <P>Such behavior is observed when Unix Splunk instance is indexing mounted Windows logs. Windows has a unique way of logging which Unix instance is not aware of causing to index with nulls "\x00". When indexing Windows logs such as iis, exchange, domain controller, and so on, install Splunk as a forwarder on the Windows box and have it forward to Unix Splunk indexer.</P> Wed, 12 May 2010 22:37:18 GMT https://community.splunk.com/t5/Splunk-Search/Why-are-some-of-the-events-garbled-with-quot-x00-quot/m-p/13334#M1217 elusive 2010-05-12T22:37:18Z https://community.splunk.com/t5/Splunk-Search/Why-are-some-of-the-events-garbled-with-quot-x00-quot/m-p/13335#M1218 <P>This also happens sometimes when the data your indexing is encoded with a different character set such as UTF-16 </P> <P>You can specify the charset in your props.conf<BR /> [somesourcetype]<BR /> CHARSET = UTF-16 </P> Thu, 13 May 2010 00:31:51 GMT https://community.splunk.com/t5/Splunk-Search/Why-are-some-of-the-events-garbled-with-quot-x00-quot/m-p/13335#M1218 Chris_R_ 2010-05-13T00:31:51Z https://community.splunk.com/t5/Splunk-Search/Why-are-some-of-the-events-garbled-with-quot-x00-quot/m-p/13336#M1219 <P>Ideally, if you are having this symptom, you should be clear about the pattern of null characters (\x00). Are they interleaved with the expected data? Do they come in small bursts (ten bytes or so)? Are there several kilobytes worth of nulls all at once?</P> Thu, 15 Jul 2010 03:20:25 GMT https://community.splunk.com/t5/Splunk-Search/Why-are-some-of-the-events-garbled-with-quot-x00-quot/m-p/13336#M1219 jrodman 2010-07-15T03:20:25Z https://community.splunk.com/t5/Splunk-Search/Why-are-some-of-the-events-garbled-with-quot-x00-quot/m-p/13337#M1220 <P>I'm seeing an input from windows onto unix having \x00 and some other unknown characters interspersed with the data. Is UTF-16 the answer to this?</P> Fri, 23 Jul 2010 22:16:14 GMT https://community.splunk.com/t5/Splunk-Search/Why-are-some-of-the-events-garbled-with-quot-x00-quot/m-p/13337#M1220 Jason 2010-07-23T22:16:14Z https://community.splunk.com/t5/Splunk-Search/Why-are-some-of-the-events-garbled-with-quot-x00-quot/m-p/13338#M1221 <P>Nope. UTF-16 turned a lot of the text into asian characters.</P> Sat, 24 Jul 2010 01:19:02 GMT https://community.splunk.com/t5/Splunk-Search/Why-are-some-of-the-events-garbled-with-quot-x00-quot/m-p/13338#M1221 Jason 2010-07-24T01:19:02Z https://community.splunk.com/t5/Splunk-Search/Why-are-some-of-the-events-garbled-with-quot-x00-quot/m-p/13339#M1222 <P>So, do we create props.conf on Forwarder TA or Indexer TA?</P> Tue, 09 Aug 2016 16:44:52 GMT https://community.splunk.com/t5/Splunk-Search/Why-are-some-of-the-events-garbled-with-quot-x00-quot/m-p/13339#M1222 sshres5 2016-08-09T16:44:52Z