Database checks: ∞% reported as Failing when counter is zero; no way to acknowledge/mute a check #1231

Setup

• Nextcloud [your version]
• MariaDB 10.11.18 on Debian 12, same VM as Nextcloud

1. Divide-by-zero shown as Failing

After FLUSH STATUS (or soon after a restart), "Table lock contention" (Table_locks_waited) shows ∞% of table locks had to wait and is marked Failing. When the denominator is zero the check should report "not enough data" or be skipped.

2. No way to acknowledge or mute a check

Some findings can't be resolved by the admin (e.g. #1224, or join/scan rates caused by Nextcloud core queries). Once investigated, there's no way to dismiss them, so they stay red indefinitely. Please consider a per-check acknowledge/mute option, ideally one that resurfaces if the value changes significantly.

Related: #1224

How to use GitHub

• Please use the 👍 reaction to show that you are affected by the same issue.
• Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
• Subscribe to receive notifications on status change and new comments.

Steps to reproduce

Expected behaviour

Tell us what should happen

Actual behaviour

Tell us what happens instead, if possible also add a screenshot

Server configuration

Web server: Apache/Nginx

Database: MySQL/Maria/SQLite/PostgreSQL

PHP version: 8.5/8.4/8.3

Nextcloud version: (see Nextcloud admin page)

If you have access to your command line run e.g.:
sudo -u www-data php occ app:list
from within your Nextcloud installation folder

If you have access to your command line run e.g.:
sudo -u www-data php occ config:list system
from within your Nextcloud installation folder

Browser

Browser name: Firefox/Chrome/Safari/…

Browser version: 124/125/…

Operating system: Windows/Ubuntu/Mac/…

Insert your browser log here, this could for example include:
a) The javascript console log
b) The network log
c) ...