https://community.splunk.com/t5/Getting-Data-In/How-to-index-data-from-a-local-process/m-p/127166#M26168 <P>I'm using a Splunk forwarder to forward data from an application running on the same Linux box as my forwarder. </P> <P>Obviously I could have my process write out all the data to disk, and have Splunk monitor these files for new data. However, the disk is already heavily loaded on this box, and this doesn't seem terribly efficient. </P> <P>Is there a better solution?</P> Thu, 10 Apr 2014 12:06:23 GMT MatMeredith 2014-04-10T12:06:23Z https://community.splunk.com/t5/Getting-Data-In/How-to-index-data-from-a-local-process/m-p/127166#M26168 <P>I'm using a Splunk forwarder to forward data from an application running on the same Linux box as my forwarder. </P> <P>Obviously I could have my process write out all the data to disk, and have Splunk monitor these files for new data. However, the disk is already heavily loaded on this box, and this doesn't seem terribly efficient. </P> <P>Is there a better solution?</P> Thu, 10 Apr 2014 12:06:23 GMT https://community.splunk.com/t5/Getting-Data-In/How-to-index-data-from-a-local-process/m-p/127166#M26168 MatMeredith 2014-04-10T12:06:23Z https://community.splunk.com/t5/Getting-Data-In/How-to-index-data-from-a-local-process/m-p/127167#M26169 <P>Going through files often is the best solution, but there are alternatives. You could have the application write syslog entries ovto the network and have Splunk receive them, or you could let the application enter data into Splunk directly through its REST API. What's best for your case depends on your case.</P> Thu, 10 Apr 2014 12:24:22 GMT https://community.splunk.com/t5/Getting-Data-In/How-to-index-data-from-a-local-process/m-p/127167#M26169 martin_mueller 2014-04-10T12:24:22Z