Feature Request: Panel to show disk utilization by file system
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- bash, python
- Domain
- observability-sre
Research direction
Start by reviewing the existing logical disk utilization implementation and related F5 Insights panel entry points, then read issue #243 to assess whether its custom REST endpoint proposal covers bash df calls. Done means agreeing on the data source and presenting filesystem utilization, including which filesystems are nearing capacity, in a usable panel.
Written by the indexing model from the issue text.
Description
One of my customers is hoping to be able to quickly see which file systems are close to full using F5 Insights (AST). The tool already shows logical disk utilization, but the customer wants to go one step deeper.
This would likely require a bash via iControl REST call (calling "df").
An example could be something like the following, though a graphical chart would be even better:
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/vg--db--vda-set.14.root 419M 97M 296M 25% /
devtmpfs 16G 4.0K 16G 1% /dev
tmpfs 16G 908M 15G 6% /dev/shm
tmpfs 16G 2.3M 16G 1% /run
tmpfs 16G 0 16G 0% /sys/fs/cgroup
/dev/mapper/vg--db--vda-set.14._usr 6.4G 5.5G 620M 90% /usr
/dev/mapper/vg--db--vda-set.14._config 2.1G 518M 1.5G 26% /config
/dev/mapper/vg--db--vda-set.14._var 4.4G 973M 3.2G 24% /var
This could also be lumped in with feature request, "Feature Request: Add Custom REST endpoints option #243", if the implementation of that request would allow for bash commands in iControl.
- Dominant language
- Python
- Stars
- 106
- Forks
- 43
- PR merge metrics
- No merged PRs in 30d
Contributor guide
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.
More from f5devcentral/application-study-tool
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
-
Difficulty 4/5 3-5 days Newbie friendliness 62/100
-
Difficulty 4/5 3-5 days Newbie friendliness 55/100
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
-
Difficulty 3/5 1-2 days Newbie friendliness 50/100
f5devcentral/application-study-tool#267 · 7 comments ·
All issues in f5devcentral/application-study-tool
Similar issues
-
documentation help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
simonw/sqlite-utils#872 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100