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

Agentic SOC Triage: Investigating Splunk ES Notables with MCP Server and a Local LLM

The Problem: Too Many Alerts, Too Little Context Security operations teams running Splunk Enterprise Security ...

All Work and No Play? Not at .conf26! Unwind at These Evening Events

Between hands-on technical sessions, keynote reveals, and diving into live architectures, .conf26 is packed ...

Join the Hackathon at .conf26 and build a No-Code AI agent

Join us for the AI Agent Buildathon, an in-person, three-hour hands-on Hackathon where you’ll use Splunk Agent ...