ExportXMLWordPrintable

      Environment

      • Zabbix server and frontend 8.0.0, PostgreSQL 16

      Steps to reproduce

      1. Create host "Web server 01" with trapper items "cpu.util", "mem.util", "disk.util" and block 1 triggers.
      2. Send "95" to "cpu.util", then "95" to "disk.util", then "95" and after that "10" to "mem.util". CPU and disk problems are open, memory problem is resolved.
      3. In Monitoring > Problems with Show "Recent problems", select CPU and memory problems and click Mass update.
      4. Enter Message "Planned maintenance window", mark Suppress, select Until, set time 3 minutes from now, click Update. Message is needed: without other operation, frontend sends only open problems to API.
      5. Do the same for disk problem alone.
      6. Wait 5 minutes and run block 2.

      1. Trigger expressions

      last(/Web server 01/cpu.util)>90
      last(/Web server 01/mem.util)>90
      last(/Web server 01/disk.util)>90
      

      2. Query

      SELECT eventid, suppress_until FROM event_suppress;
      

      Result

      CPU problem stays suppressed after selected time. Its update history shows selected time.

      Check Result
      CPU problem, "acknowledges.suppress_until" selected time
      CPU problem, suppression task and "event_suppress.suppress_until" 0 (indefinitely)
      Disk problem, updated alone suppression ends at selected time
      Same steps, resolved problem created before open one open problem is not suppressed, history shows "Suppressed"

      Expected

      CPU problem is suppressed until selected time.

            Assignee:
            Zabbix Development Team
            Reporter:
            Piotr Wegrzyn
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: