Cherry-pick #7986 to 6.x: Better tracking of number of open file descriptors of Filebeat #8514
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.
Cherry-pick of PR #7986 to 6.x branch. Original message:
New metrics are introduced to better track the number of open file descriptors.
In the initial issue number of open file descriptors were requested by input. Reporting the number of open files by harvesters is already implemented. It's reported as
filebeat.harvester.open_files
.I included process level file descriptor information reporting for each Beat which runs on Linux.
New metrics
beat.fd.open
: Number of open files by a Beat process.It's the number of files under
/proc/{{ filebeat-pid }}/fd
. Only implemented on Linux.beat.fd.limit.soft
: Soft limit of the Beat process.Could be used to notify a user if the process is reaching the limit (in the Monitoring UI).
beat.fd.limit.hard
: Hard limit of the Beat process.It is the max limit that can be set on a host without modifying kernel params.