You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It sounds like our general recommendation when dealing with file rotation is to avoid using symlinks. Instead of using a symlink in the prospector path definition, we recommend pointing the harvester to the original file(s) and with the path pattern match the file data is written to and all its rotated files.
It will be helpful to add a note here upfront, esp. since later on the same page, we provide an option for the harvester to handle symlinks - which is disabled by default.
The text was updated successfully, but these errors were encountered:
It sounds like our general recommendation when dealing with file rotation is to avoid using symlinks. Instead of using a symlink in the prospector path definition, we recommend pointing the harvester to the original file(s) and with the path pattern match the file data is written to and all its rotated files.
It will be helpful to add a note here upfront, esp. since later on the same page, we provide an option for the harvester to handle symlinks - which is disabled by default.
The text was updated successfully, but these errors were encountered: