Uploaded image for project: 'ZABBIX FEATURE REQUESTS'
  1. ZABBIX FEATURE REQUESTS
  2. ZBXNEXT-18

Send an alert after trigger being acknowledged

    XMLWordPrintable

Details

    • Team C
    • Sprint 4, Sprint 5, Sprint 6, Sprint 7, Sprint 8, Sprint 9, Sprint 10, Sprint 11, Sprint 12, Sprint 13, Sprint 14, Sprint 30, Sprint 31, Sprint 32
    • 28

    Description

      Alexei,we need to have Email alert sent out to our team of Admins and Customers. letting them know that the triggered Alert has been acknowledged When acknowledged. i cant seem to effectively set this up in a manner of that when i acknowledge an alert no action takes place and no email is sent to the given group.

      how do i go about setting up an action to get this work correctly

      Attachments

        1. multi_trigger_ack.png
          multi_trigger_ack.png
          66 kB
        2. select_button.png
          select_button.png
          56 kB
        3. zbxnext_31.png
          zbxnext_31.png
          82 kB
        4. ZBXNEXT-18.jpg
          ZBXNEXT-18.jpg
          128 kB
        5. zbxnext-18.postman_collection.json
          65 kB
        6. ZBXNEXT-18-2.jpg
          ZBXNEXT-18-2.jpg
          81 kB
        7. ZBXNEXT-18-3.jpg
          ZBXNEXT-18-3.jpg
          224 kB
        8. zbxnext-18-clone2.jpg
          zbxnext-18-clone2.jpg
          221 kB
        9. zbxnext-18-empty.jpg
          zbxnext-18-empty.jpg
          172 kB

        Issue Links

          causes

          Problem report - Problem report ZBX-13570 Undefined index in API call

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed
          depends on

          New Feature Request - A new feature request of the product, which has yet to be developed. ZBXNEXT-4100 Recovery operations messages for ‘all involved’ users

          • Trivial - Cosmetic problem like misspelt words or misaligned text.
          • Open

          Change Request - An Change Request or enhancement Improvement to an existing feature or task. ZBXNEXT-4084 Notify all after trigger being acknowledged

          • Major - Major loss of function.
          • Closed

          Change Request - An Change Request or enhancement Improvement to an existing feature or task. ZBXNEXT-3926 Misleading {TRIGGER.STATUS} value in notifications

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed

          Change Request - An Change Request or enhancement Improvement to an existing feature or task. ZBXNEXT-4113 Zabbix user with read access can acknowledge

          • Trivial - Cosmetic problem like misspelt words or misaligned text.
          • Closed
          is duplicated by

          New Feature Request - A new feature request of the product, which has yet to be developed. ZBXNEXT-274 Acknowledge notifications

          • Major - Major loss of function.
          • Closed

          New Feature Request - A new feature request of the product, which has yet to be developed. ZBXNEXT-3303 Add action for acknowledging issues

          • Trivial - Cosmetic problem like misspelt words or misaligned text.
          • Closed

          Change Request - An Change Request or enhancement Improvement to an existing feature or task. ZBXNEXT-3261 Do action when acknowledge the event

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed

          Incident report - Incident report ZBX-12189 Actions with ' Event acknowledged = Ack' Operation not working

          • Major - Major loss of function.
          • Closed

          Activity

            People

              s.paskevics Sergejs Paskevics
              sarioto Sol Arioto
              Votes:
              96 Vote for this issue
              Watchers:
              61 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: