Add an option to respect filesystem locks to the filelog receiver. #34801
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description: Add an option to respect filesystem locks to the filelog receiver.
When enabled otelcol will attempt to acquire a shared lock on files before reading them. If it is unable to acquire that lock it will ignore the file until the next poll cycle.
This feature is only implemented for Unix - on other platforms it is a no-op.
Link to tracking Issue: None
Testing: Manual testing was done on a laptop running macOS Sonoma 14.6.1. I verified that otelcol will not read a file that is actively locked by another process, and that it will proceed with reading once the lock is released.
Documentation: Added documentation for the filelog receiver describing this option.