NETWAYS / NETWAYS/check_system_basics
[Feature]: Filesystem differences/philosophies and metrics
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9
- Forks
- 3
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 4
Description
Describe the feature request
It recently came to my attention, that a fixed number of inodes is only a characteristic of some file system, not all of them.
In this case it was btrfs which allocates inodes dynamically (and where the remaining space is more difficult to measure).
The general problem of different filesystem characteristics is far more extensive, there might be questions about the consistency of the journal or quotas instead of "physical" limits.
In general there are some things to consider for now and in the future:
- There has to some filesystem-specific path for some measurements/tests
- What can go wrong in a specific filesystem and should therefore be monitored?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The request names no files, tests, or entry points. Start by mapping the existing filesystem measurements and tests, then document which filesystem-specific metrics and failure modes need support. Done means the supported filesystem differences and monitoring scope are agreed and covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, linux
- Domain
- observability-sre, operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100