Getting Data In

Why UF think my file is binary?

yutaka1005
Builder

In my environment, UF monitors the file and forwards it to Splunk.

It was able to capture the file without problems before,
Due to the version upgrade of software that outputs log that was being monitored,
and the character code is changed from Shift_jis to utf-16LE (with BOM), it is no longer imported.

When checking the internal log of UF, message saying "it was a binary file, so ignored it".

Is this a bug?
Is there any workaround other than updating?

If anyone knows, it would be greatly appreciated if you could tell me.

UF ver: 6.2.0

0 Karma
1 Solution

mayurr98
Super Champion

hey

specify this attribute in props.conf

[host::my-foreign-docs]
CHARSET=AUTO

http://docs.splunk.com/Documentation/Splunk/6.3.3/data/Configurecharactersetencoding#Automatically_s...

Also put this

NO_BINARY_CHECK = [true|false]
* When set to true, Splunk processes binary files.
* Can only be used on the basis of [<sourcetype>], or [source::<source>],
  not [host::<host>].
* Defaults to false (binary files are ignored).
* This setting applies at input time, when data is first read by Splunk.
  The setting is used on a Splunk system that has configured inputs
  acquiring the data.

let me know if this helps!

View solution in original post

0 Karma

mayurr98
Super Champion

hey

specify this attribute in props.conf

[host::my-foreign-docs]
CHARSET=AUTO

http://docs.splunk.com/Documentation/Splunk/6.3.3/data/Configurecharactersetencoding#Automatically_s...

Also put this

NO_BINARY_CHECK = [true|false]
* When set to true, Splunk processes binary files.
* Can only be used on the basis of [<sourcetype>], or [source::<source>],
  not [host::<host>].
* Defaults to false (binary files are ignored).
* This setting applies at input time, when data is first read by Splunk.
  The setting is used on a Splunk system that has configured inputs
  acquiring the data.

let me know if this helps!

0 Karma

yutaka1005
Builder

Thank you for answer mayurr98.

As a result of setting like below,
similar events did not recur.

[<sourcetype name>]
CHARSET=utf-16le
NO_BINARY_CHECK = true

It was very helpful!

0 Karma

inventsekar
Super Champion
0 Karma
Get Updates on the Splunk Community!

Improve Your Security Posture

Watch NowImprove Your Security PostureCustomers are at the center of everything we do at Splunk and security ...

Maximize the Value from Microsoft Defender with Splunk

 Watch NowJoin Splunk and Sens Consulting for this Security Edition Tech TalkWho should attend:  Security ...

This Week's Community Digest - Splunk Community Happenings [6.27.22]

Get the latest news and updates from the Splunk Community here! News From Splunk Answers ✍️ Splunk Answers is ...