TCP Port Checker. Splunk Cloud. Overview. Details. A high performance TCP Port Check input that uses python sockets. Designed for high volume concurrent testing, and utilizes a CSV file for targets. Data written with minimal raw size (license usage), and utilizes indexed extractions for maximum performance with tstats. Modular Inputs 2 • Extend the Splunk framework to define a custom input capability, just like the standard inputs you are familiar with (TCP/UDP/File etc) • Splunk treats your custom input definitions as if they were part of Splunk's native inputs, totally integrated first class citizen objects in Splunk • Users interactively create. The four major queues in the data input pipeline are parsing, merging, typing, and index. Data flows through the queues in the following order and each one contains different processes that take place within them. Parsing queue. UTF-8 - character encoding. Line Breaker - breaks down the events into separate lines. Configuring Data Input with Red Hat Ansible Content Collections. To receive the Ansible Tower logs in Splunk, we need to create a Data Input TCP. To do that we will use the Splunk Enterprise Security Content Collection available on Automation Hub as part of the Red Hat-Maintained Content Collections release. The TcpSplunkInput class represents a Splunk-processed "cooked" TCP data input. This differs from a raw TCP input in that this cooked TCP data is processed by Splunk and is not in raw form. Nested Class Summary . Nested classes/interfaces inherited from interface java.util.Map; java.util.Map.Entry<K,V>.