Filebeat close and clean configuration methods
This article mainly explains the "filebeat close and clean configuration method", the content of the article is simple and clear, easy to learn and understand, now please follow the editor's ideas slowly in depth, together to study and learn "filebeat close and clean configuration method" bar!
Close and clean configurations take effect only if there is no path match and inode information is available.
A file that does not match path cannot be obtained if it has been updated by close, and will be obtained at the breakpoint when renamed to match (because the registration file saves its state inode and offset).
When close and ignore, when renamed to match, the previous update of ignore will not be obtained. When a new update is generated, it will be obtained from the previous breakpoint.
When close and ignore and clean, it cannot be obtained when renamed to match.
Filebeat.inputs:- type: log # Change to true to enable this input configuration. Enabled: true # Paths that should be crawled and fetched. Glob based paths. Paths:-/ home/admin/statistics/logdyb/statis.log-/ home/admin/statistics/logdyb/statis.log.*.retry # in the log4j log rename scenario, when the synchronization service filebeat fails to resume, the breakpoint retransmission can be achieved by renaming the log to .retry; # the valid time for retransmission is ignore_older, and the time for manual updates to trigger retransmission is limited to clean_inactive. Exclude_files: [.completed $'] encoding: utf-8 tail_files: false close_inactive: 30m close_removed: false clean_removed: false ignore_older: 72h clean_inactive: 168h Thank you for reading, the above is the content of "filebeat close and clean configuration method". After the study of this article, I believe you have a deeper understanding of the filebeat close and clean configuration method, and the specific use needs to be verified in practice. Here is, the editor will push for you more related knowledge points of the article, welcome to follow!
