Suppress Selected Discovery Trigger Alerts on Specific Hosts During High Load Periods

[hugo.raddon]

Hi,

We face an issue where evening data load processes and early-morning data aggregation cause disk alert triggers (generated via discovery) to fire. While maintenance windows for tagged CPU and Memory triggers works well in supressing those alerts, disk alerts remain problematic.

I attempted to add tags to disk triggers via an override on the "Physical disks discovery" rule. However, the {HOST.HOST} filter isn’t available, forcing me to clone the template for each affected host. Even with a dedicated template and a Physical disks discovery override, the additional tag isn’t propagating to the host triggers. One override is configured as follows:

• Filter: {#FSNAME} matches H:
• Operation:
  • Object: Trigger prototype
  • Condition: contains "Disk is overloaded"
  • Tags: 'DataLoad' - 'Evening'

We're running Zabbix V7 LTS. I noticed this thread on template tag inheritance (https://www.zabbix.com/forum/zabbix-...ce-not-working), but my scenario appears different.

Is there a better way to suppress selected alerts during known periods of high system activity? Specifically, how can I tag triggers created via discovery on specific hosts for maintenance windows?

Many thanks,

Hugo

[hugo.raddon]

Hi,

Just giving this post a bump, any helpful thoughts, comments and suggestions would be appreciated. The current workaround it to put the whole server into maintenance mode during periods of heavy load which means we lose alerts for other issues as well which isn't ideal.

Many thanks,

Hugo