Splunk Search

Converting strings

mborner
Explorer

I've got email subjects extracted into a field, which are encoded in UTF-8 or ISO-8859-*

Examples:

=?ISO-8859-15?Q?Video:_Hei=DFes_Photo-Shooting_Miley_Cyrus!_?= =?ISO-8859-15?Q?Olala!?=

or

=?UTF-8?Q?Tr:_La_beaut=C3=A9...?=

What would be the best way to convert these into a readable format?

Tags (1)

Ron_Naken
Splunk Employee
Splunk Employee

You can configure character set encoding. Here is the manual page that describes how: http://www.splunk.com/base/Documentation/4.1.7/Admin/Configurecharactersetencoding

landen99
Motivator

Let's say that we want to create a field which is simply an original field decoded into ASCII and we want that process to happen internally within Splunk. How do we do that?

mborner
Explorer

It was not exactly was I was looking for. The logfile is in ASCII, but it contains fields that are MIME encoded.

To solve the problem I wrote an external command, that decodes MIME fields into utf-8.

Get the code here:

http://pastebin.com/vtWnL50z

tomasmoser
Contributor

Try MIME Decoder TA add-on:
https://splunkbase.splunk.com/app/5116/

Tags (3)
0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...