Getting Data In

How to print unicode as unicode?

wegscd
Contributor

I have a JSON data source with data like this:

{"download.doc_title": "GCP-7 R\u00f3znorodnosc, R\u00f3wne Szanse Oraz Szacunek W Miejscu Pracy.pdf"}

If I look at the event syntax highlighted, it renders as I would expect:

{   [-] 
     download.doc_title:     GCP-7 Róznorodnosc, Równe Szanse Oraz Szacunek W Miejscu Pracy.pdf   
}

...but when I run any reports against, it shows up in the browser with the unicode escapes, instead of the unicode characters:

<searchcriteria> | table download.doc_title

shows

GCP-7 R\u00f3znorodnosc, R\u00f3wne Szanse Oraz Szacunek W Miejscu Pracy.pdf

how do I get it to show the Polish rendition?

GCP-7 Róznorodnosc, Równe Szanse Oraz Szacunek W Miejscu Pracy.pdf
0 Karma

ddrillic
Ultra Champion

Similar issue at Best practice for dealing with Unicode codepoints in Splunk ?

But not much help there...

0 Karma

MousumiChowdhur
Contributor
0 Karma

MousumiChowdhur
Contributor

Please set CHARSET = AUTO in your props.conf

0 Karma

wegscd
Contributor

The data is apparently being parsed correctly (remember, it displays correctly when syntax is highlighted). Will charset = auto affect parsing or display?

0 Karma

MousumiChowdhur
Contributor

Hi @wegscd!
It affects parsing.

0 Karma

wegscd
Contributor

The data has been parsed correctly. This is a display side issue.

0 Karma
Get Updates on the Splunk Community!

Splunk Enterprise Security: Your Command Center for PCI DSS Compliance

Every security professional knows the drill. The PCI DSS audit is approaching, and suddenly everyone's asking ...

Developer Spotlight with Guilhem Marchand

From Splunk Engineer to Founder: The Journey Behind TrackMe    After spending over 12 years working full time ...

Cisco Catalyst Center Meets Splunk ITSI: From 'Payments Are Down' to Root Cause in ...

The Problem: When Networks and Services Don't Talk Payment systems fail at a retail location. Customers are ...