The alerting rule is set to resolve once storage has dropped below 80%. I can silence the alarm by removing the unique resolution rule.
Oddly, this is still firing after logs have been rotated and images have been pruned:
```
$ df -h
Filesystem Size Used Avail Use% Mounted on
udev 7.8G 0 7.8G 0% /dev
tmpfs 1.6G 2.0M 1.6G 1% /run
/dev/vda1 16G 7.7G 7.3G 52% /
tmpfs 7.9G 0 7.9G 0% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
/dev/vda15 124M 12M 113M 10% /boot/efi
tmpfs 1.6G 0 1.6G 0% /run/user/1000
...
```
The alerting rule is set to resolve once storage has dropped below 80%. I can silence the alarm by removing the unique resolution rule.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
I am getting a lot of alarms for excessive disk use on this worker. In truth, all of the workers probably should be upgraded to 32GB disks.
Oddly, this is still firing after logs have been rotated and images have been pruned:
The alerting rule is set to resolve once storage has dropped below 80%. I can silence the alarm by removing the unique resolution rule.
I restarted the prometheus-node-exporter service and the fields updated successfully.