MicroOS health-checker notification filtering for transactional-update

openSUSE MicroOS utilizes a health-checker script that executes following a transactional-update reboot to verify system integrity. This process is governed by the configurations defined in /etc/health-checker.conf.

Currently, the health-checker triggers email notifications for any failed check regardless of the impact. There is no native mechanism within the transactional-update framework to distinguish between critical system failures and non-critical warnings, such as disk usage thresholds. This lack of severity-based filtering can lead to notification noise during routine update cycles.

Given the behavior in transactional-update 3.5, what are the recommended strategies for implementing severity filtering without modifying the core system scripts? Can notification urgency be managed through /etc/health-checker.conf, or is external mail filtering required to suppress warning-level alerts?