Merge pull request #243029 from JeffreyWolford/patch-15

Update data-collection-text-log.md

Author: prmerger-automator[bot]

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

@@ -25,11 +25,11 @@ To complete this procedure, you need:
     - 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. 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. 
+    - Do clean up all log files in the monitored directory. Tracking many log files can drive up agent CPU and Memory usage. Wait for at least 2 days to allow ample time for all logs to be processed.
+    - Do Not overwrite an existing file with new records. You should only append new records to the end of the file. Overwriting will cause data loss.
+    - Do Not rename a file to a new name and then open a new file with the same name. This could cause data loss.
+    - Do Not rename or copy large log files that match the file scan pattern in to the monitored directory. If you must, do not exceed 50MB per minute.
+    - Do Not rename a file that matches the file scan pattern to a new name that also matches the file scan pattern. This will cause duplicate data to be ingested. 
 
 
 ## Create a custom table