Getting Data In

handle scripted input as single line values

jan_wohlers
Path Finder

Hi Splunkies,

another question by me... I run a script every 15 min which counts DFS connections on different servers. the output of this script looks pretty much this way in the search app using source="dfs_connections" searchstring.

DFSConnection_ServerA=2658
DFSConnection_ServerB=1554
DFSConnection_ServerC=1217
DFSConnection_ServerD=242
DFSConnection_ServerE=680
DFSConnection_ServerF=639
...

If i copy the text and paste it here, it will look like

DFSConnection_ServerA=2658DFSConnection_ServerB=1554DFSConnection_ServerC=1217DFSConnection_ServerD=242DFSConnection_ServerE=680DFSConnection_ServerF=639 ...

I realize that the values aren't splitted... I try to create a timechart (linechart) that shows the dfs connection (each 15 min) for each Server. So I can see peeks during the week.

How can I seperate the Values, so splunk knows, that each ServerX=1234 line is a single value?

I hope you understand my problem and you can give me a hint!

Thanks in advance!

Jan

0 Karma

yannK
Splunk Employee
Splunk Employee

To fix the issue at the origin:
You can change your script to add a line break at the end of each output.
or in the sourcetype of your script add : SHOULD_LINEMERGE=false

To fix it at search time,
try to reformat your event, and force a key value extraction

mysearch | rex mode=sed "s/DFSConnection/ DFSConnection/g" | extract pairdelim=" " kvdelim="="

see http://docs.splunk.com/Documentation/Splunk/4.3.3/SearchReference/Extract

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 ...