Skip to content

Commit d2b2bea

Browse files
Update data-collection-text-log.md
------- cc: @guywi-ms
1 parent b82169f commit d2b2bea

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

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

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -21,14 +21,14 @@ To complete this procedure, you need:
2121
- A VM, Virtual Machine Scale Set, or Arc-enabled on-premises server that writes logs to a text file.
2222

2323
Text file requirements and best practices:
24-
- Do store files on the local drive of the machine on which Azure Monitor Agent is running.
24+
- 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.
2525
- Do delineate the end of a record with an end of line.
2626
- Do use ASCII or UTF-8 encoding. Other formats such as UTF-16 aren't supported.
2727
- Do create a new log file every day so that you can remove old files easily.
2828
- 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.
2929
- Do Not overwrite an existing file with new data. You should only append new data to the file.
30-
- Do Not rename a file and open a new file with the same name to log to.
31-
- Do Not rename or copy large log files in to the monitored directory.
30+
- Do Not rename a file and open a new file with the same name to log to.
31+
- Do Not rename or copy large log files in to the monitored directory. If you must, do not exceed 50MB per minute
3232
- 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.
3333

3434

0 commit comments

Comments
 (0)