Scripted Input is incomplete

siva_cg · ‎06-05-2018

Hi Team,

I have deployed a scripted input which will list out all .log files from a specific folder on application server (Universal Forwarder). It is running as expected but I am not able to see full output in indexers.

For example, if we have 80 lines in the output on UF, we are able to see only 18 lines on Search Heads. Manual running of script is giving the output as expected.

Could you please help me to resolve the issue by deploying any configuration limits to index full output? Thanks in advance.

ansif · ‎06-08-2018

What script you are using?

Scripted Input is incomplete

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

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

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

Build resilience for the agentic era: Join us at Splunk Go San Jose

Manage Edge Processor pipelines end to end with APIs

Join the Conversation

Scripted Input is incomplete

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

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

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

Build resilience for the agentic era: Join us at Splunk Go San Jose

Manage Edge Processor pipelines end to end with APIs