Steps to reproduce:

1. Create host linked "Template Module Linux filesystems by Zabbix agent"
2. Add override configuration to Low Discovery rules "Mounted filesystem discovery" in "Template Module Linux filesystems by Zabbix agent" as follows:

   #	Name	If filter matches	Filter	(Operations)Object	(Operations)Condition	(Operations)Severity
   1:	overrides 1	Stop processing	{#FSNAME} matches /boot	Trigger prototype	contains Disk space is low	Disaster
   2:	overrides 2	Stop processing	{#FSNAME} matches /	Trigger prototype	contains Disk space is low	Information

3. Wait performed Low Discovery rules "Mounted filesystem discovery"
4. Check trigger that created from trigger prototype

Result:
See screenshot

"overrides 1" filter matched, but processed "overrides 2".
Both trigger severity overried as follows:

• /: Disk space is low (used > {$VFS.FS.PUSED.MAX.WARN:"/boot"}%)
• /boot: Disk space is low (used > {$VFS.FS.PUSED.MAX.WARN:"/boot"}%)

Expected:
Expect filter matched /boot, stop processing override severity of trigger "/: Disk space is low (used > {$VFS.FS.PUSED.MAX.WARN:"/boot"}%)".
Override only severity of trigger "/boot: Disk space is low (used > {$VFS.FS.PUSED.MAX.WARN:"/boot"}%)".