title: Date in NLog file name and limit the number of log files
body: <p>I'd like to achieve the following behaviour with NLog for rolling files:<br>
   1. prevent renaming or moving the file when starting a new file, and<br>
   2. limit the total number or size of old log files to avoid capacity issues over time</p>
  
  <p>The first requirement can be achieved e.g. by adding a timestamp like <code>${shortdate}</code> to the file name. Example:  </p>
  
  <pre><code>logs\trace2017-10-27.log &lt;-- today's log file to write   
  logs\trace2017-10-26.log  
  logs\trace2017-10-25.log  
  logs\trace2017-10-24.log &lt;-- keep only the last 2 files, so delete this one 
  </code></pre>
  
  <p>According to other posts it is however not possible to use date in the file name and archive parameters like <code>maxArchiveFiles</code> together. If I use <code>maxArchiveFiles</code>, I have to keep the log file name constant:  </p>
  
  <pre><code>logs\trace.log &lt;-- today's log file to write   
  logs\archive\trace2017-10-26.log  
  logs\archive\trace2017-10-25.log  
  logs\archive\trace2017-10-24.log &lt;-- keep only the last 2 files, so delete this one 
  </code></pre>
  
  <p>But in this case every day on the first write it moves the yesterday's trace to archive and starts a new file.</p>
  
  <p>The reason I'd like to prevent moving the trace file is because we use Splunk log monitor that is watching the files in the log folder for updates, reads the new lines and feeds to Splunk.</p>
  
  <p>My concern is that if I have an event written at 23:59:59.567, the next event at 00:00:00.002 clears the previous content before the log monitor is able to read it in that fraction of a second.</p>
  
  <p>To be honest I haven't tested this scenario as it would be complicated to set up as my team doesn't own Splunk, etc. - so please correct me if this cannot happen.</p>
  
  <p>Note also I know that it is possible to directly feed Splunk other ways like via network connection, but the current setup for Splunk at our company is reading from log files so it would be easier that way.</p>
  
  <p>Any idea how to solve this with NLog?</p>