Getting Data In

What are the advantages and disadvantages of using scripted input vs file input ?

dheeran
Engager

I am having a scenario where a script can either produce a csv or a stdout.
Which is the best route to ingest this data?

The dataset in question is employee information where we do not expect a huge number of new records every day.

Thanks in advance
Siva

0 Karma
1 Solution

ivanreis
Builder

I would suggest to produce the csv instead of stdout. If you lose any network connectivity the data you are trying to run thought stdout can be lost, if you do not have any buffer to store this data.
According to the Splunk Administration manual, this is the only the downside of using scripting inputs.
"One possible downside to scripted input is potential loss of data
– Example: the forwarder that is running the script is not able to connect to the indexer due to networking problems".

View solution in original post

ivanreis
Builder

I would suggest to produce the csv instead of stdout. If you lose any network connectivity the data you are trying to run thought stdout can be lost, if you do not have any buffer to store this data.
According to the Splunk Administration manual, this is the only the downside of using scripting inputs.
"One possible downside to scripted input is potential loss of data
– Example: the forwarder that is running the script is not able to connect to the indexer due to networking problems".

Career Survey
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.
Get Updates on the Splunk Community!

Splunk AI Assistant for SPL vs. ChatGPT: Which One is Better?

In the age of AI, every tool promises to make our lives easier. From summarizing content to writing code, ...

Data Persistence in the OpenTelemetry Collector

This blog post is part of an ongoing series on OpenTelemetry. What happens if the OpenTelemetry collector ...

Thanks for the Memories! Splunk University, .conf25, and our Community

Thank you to everyone in the Splunk Community who joined us for .conf25, which kicked off with our iconic ...