No problem,
We can keep this forum thread open, and when a fix is provided I will respond to here.
UPDATE:
We have found a fix for this issue, but it won't be released until version 2.0.3. We do however, have a workaround in the meantime (NOTE: this change will not be applied to upgrade changes)
Since you are receiving these by eventlogs. Go to the NLS home page --> Click
Configure --> click Global Config --> Open up The
Windows Event Logs Inputs -->
Delete the
{ charset = xxxx }.
The final input should look like this.
Code: Select all
tcp {
type => 'eventlog'
port => 3515
codec => json
}
Once you can verify it looks like this, please click
Save & Apply
Wait for traditional Chinese characters to come in, and verify the solution.