Getting Data In

Search script - stdin contents

Sqig
Path Finder

Hi. I'm starting to work with custom search commands. For now, I need to use Perl.

Just to get started, I did a simple thing to read STDIN and dump the results to a text file on the system.

Along with the actual Results data I expected to see, I see things that start with some of this stuff (usually followed by things that are part of my actual Splunk search:
keywords: (+ elements of my search)
search:search%20 (+ my search)
sharedStorage: (location of my pooled search head shared storage)

The painful part of this is that this extra info is interspersed with the rest of my actual search results, so it's not like I can skip lines until I start seeing valid data.

I haven't found any information on exactly why this data appears in STDIN.

Can anyone shed light on this or at least point me towards some documentation that I may have missed?

Thank you.

Tags (2)
0 Karma
1 Solution

Sqig
Path Finder

I think I found the answer to this one. It looks like if I specify the following on commands.conf, I don't get the extra information:

enableheader = false

View solution in original post

0 Karma

alexl1
Path Finder

how do u get stdin to go to perl?

0 Karma

Sqig
Path Finder

I think I found the answer to this one. It looks like if I specify the following on commands.conf, I don't get the extra information:

enableheader = false

0 Karma
Get Updates on the Splunk Community!

Introducing the 2024 SplunkTrust!

Hello, Splunk Community! We are beyond thrilled to announce our newest group of SplunkTrust members!  The ...

Introducing the 2024 Splunk MVPs!

We are excited to announce the 2024 cohort of the Splunk MVP program. Splunk MVPs are passionate members of ...

Splunk Custom Visualizations App End of Life

The Splunk Custom Visualizations apps End of Life for SimpleXML will reach end of support on Dec 21, 2024, ...