Merge pull request #232744 from JeffreyWolford/patch-8

Update data-collection-text-log.md

Author: prmerger-automator[bot]

articles/azure-monitor/agents/data-collection-text-log.md

@@ -21,14 +21,14 @@ To complete this procedure, you need:
 - A VM, Virtual Machine Scale Set, or Arc-enabled on-premises server that writes logs to a text file.
 
     Text file requirements and best practices:    
-    - Do store files on the local drive of the machine on which Azure Monitor Agent is running. 
+    - Do store files on the local drive of the machine on which Azure Monitor Agent is running and in the directory that is being monitored.
     - Do delineate the end of a record with an end of line. 
     - Do use ASCII or UTF-8 encoding. Other formats such as UTF-16 aren't supported.
     - Do create a new log file every day so that you can remove old files easily. 
     - Do clean up all log files older than 2 days in the monitored directory. Azure Monitor Agent does not delete old log files and tracking them uses up Agent resources.
     - Do Not overwrite an existing file with new data. You should only append new data to the file.
-    - Do Not rename a file and open a new file with the same name to log to.
-    - Do Not rename or copy large log files in to the monitored directory.
+    - Do Not rename a file and open a new file with the same name to log to. 
+    - Do Not rename or copy large log files in to the monitored directory. If you must, do not exceed 50MB per minute
     - Do Not rename files in the monitored directory to a new name that is also in the monitored directory. This can cause incorrect ingestion behavior.