There is no interval. The forwarder sends data as soon as it has anything to send. You should expect some minor delay before you see the data in your index since data needs to move through the various queues in both the forwarder and the indexer, though. The inputs your forwarder is configured with might use some kind of intervals, like scripted inputs or WMI based inputs.
There is no interval. The forwarder sends data as soon as it has anything to send. You should expect some minor delay before you see the data in your index since data needs to move through the various queues in both the forwarder and the indexer, though. The inputs your forwarder is configured with might use some kind of intervals, like scripted inputs or WMI based inputs.
What's in your environment that makes it a bad idea to send the data as soon as it arrives to the forwarder?
If the log constantly changes, then it would be expensive to send a TCP traffic every time it changes.
To achieve that you'd need to use a scripted input that only reads the data once an hour. There's some stuff on it here: http://splunk-base.splunk.com/answers/59916/can-you-set-a-certain-time-forwarding-occurs
Then how do I configure Splunk Universal forwarder to send data every one hour to main Instance?