Currently Zabbix maintenance mode applies only to hosts or host groups.

In many operational scenarios, administrators need to perform planned maintenance on a specific service or application component without suppressing all monitoring for the host.

Example:

• A web server has monitoring for CPU, memory, disk, SSH, Apache, PHP-FPM and application checks.
• During an Apache upgrade/restart, only Apache-related triggers should be suppressed.
• Other host monitoring should continue generating alerts.

Proposed feature:
Allow users to place individual triggers (or trigger tags/services) into maintenance/suppression mode for a defined period, without affecting the entire host.

Possible implementation:

• Add "maintenance/suppress trigger" option.
• Allow scheduling by trigger, trigger tag, or service.
• Keep event history and audit information.