Repository navigation
[Bug]: Useless "Alerts" cannot be disabled or configured to be useful #1268
Description
⚠️ This issue respects the following points: ⚠️
- This is not a troubleshooting question, general support matter, or webserver/proxy problem, but likely a bug (if unsure, ask the Community Help Forum).
- This issue is not already reported on Github OR solved at the Community Help Forum (I've searched!).
- I'm using a maintained major version of Nextcloud Server and tested against the latest patch level. (Supported major versions and current patch levels).
- I agree to follow Nextcloud's Code of Conduct.
- I've tried my best to provide clear reproduction steps that someone unfamiliar with this bug could use to reproduce it.
Bug description
"Security & setup warnings" show 1 warning.
Database configuration
1 database check is failing.
Buffer cache hit ratio
Warning
·
pg.cache_hit_ratio
Failing
A significant share of page reads are missing the shared buffer cache.
Cache hit ratio is 98.2944%; aim for 99% or higher.
Who thought it is a great idea to clutter the UI with absolutely senseless alerts?
Why cannot i disable this monitoring?
Why cannot i configure(!) the warning limit?
Why cannot i permanently acknowledge the useless "warning"?
Why does my DB need a 99% cache hit ratio, just so that my UI isn't cluttered with warning that provide nothing, except triggering people's OCD?
Steps to reproduce
Have a super small Nextcloud Server for 1 person, that hosts your phone's contacts and calendar.
But broooo you need 1-2GB postgre cache, otherwise we show yellow warnings in your admin UI!
Expected behavior
NOT showing warnings, when there is nothing to warn me about. or at least let me chose to disable this unwanted monitoring!
Nextcloud Server version
35
Operating system
Debian/Ubuntu
PHP engine version
PHP 8.4
Web server
Apache (supported)
Database engine version
PostgreSQL
Is this bug present after an update or on a fresh install?
Updated from a MINOR version (ex. 32.0.1 to 32.0.2)
Are you using the Nextcloud Server Encryption module?
None
What user-backends are you using?
- Default user-backend (database)
- LDAP/ Active Directory
- SSO - SAML
- Other
Configuration report
List of activated Apps
Nextcloud Signing status
Nextcloud Logs
Additional info
No response
Activity
kesselb commentedon Nov 9, 2026
Thanks for the report! Being able to acknowledge or mute a check is already requested in #1231, so I'm closing this as a duplicate to keep the discussion in one place. I've noted your other two points there as well: a configurable limit, and that a 99% cache hit ratio is too strict for small instances.