https://community.splunk.com/t5/Monitoring-Splunk/log-file-rotate-and-flush-conundrum/m-p/450060#M6123 <P>Monitor the rolled logs as well and ensure you're not using <CODE>crcSalt = &lt;SOURCE&gt;</CODE>. When you monitor the rolled logs as well, Splunk would know that it's a copy of the file already ingested (the CRC for the file would be same even if it's renamed) and would not re-ingest whole file again, just the new/missed content. You don't want to use <CODE>crcSalt = &lt;SOURCE&gt;</CODE> as it'll force the CRC to be generated based on full file path and the file path will change when you rename it, causing a re-ingestion.</P> Thu, 09 May 2019 14:53:41 GMT somesoni2 2019-05-09T14:53:41Z https://community.splunk.com/t5/Monitoring-Splunk/log-file-rotate-and-flush-conundrum/m-p/450059#M6122 <P>Splunk forwarder monitors a file named AppLogs.txt. 3 times a day, a cron job copies the original file to a backup AppLogs.txt.timestamp and flushes the original file. Between the copy to backup and flush, the application writes some more logs into the original AppLogs.txt which is not captured by the splunk forwarder and lost when the original file is flushed. What would be the ideal solution to solve this problem?</P> Thu, 09 May 2019 09:40:42 GMT https://community.splunk.com/t5/Monitoring-Splunk/log-file-rotate-and-flush-conundrum/m-p/450059#M6122 pkd18 2019-05-09T09:40:42Z https://community.splunk.com/t5/Monitoring-Splunk/log-file-rotate-and-flush-conundrum/m-p/450060#M6123 <P>Monitor the rolled logs as well and ensure you're not using <CODE>crcSalt = &lt;SOURCE&gt;</CODE>. When you monitor the rolled logs as well, Splunk would know that it's a copy of the file already ingested (the CRC for the file would be same even if it's renamed) and would not re-ingest whole file again, just the new/missed content. You don't want to use <CODE>crcSalt = &lt;SOURCE&gt;</CODE> as it'll force the CRC to be generated based on full file path and the file path will change when you rename it, causing a re-ingestion.</P> Thu, 09 May 2019 14:53:41 GMT https://community.splunk.com/t5/Monitoring-Splunk/log-file-rotate-and-flush-conundrum/m-p/450060#M6123 somesoni2 2019-05-09T14:53:41Z