[ZBX-23051] PagerDuty Integration. Event Orchestration Created: 2023 Jul 03  Updated: 2024 Apr 10  Resolved: 2023 Aug 25

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: None
Affects Version/s: None
Fix Version/s: 6.0.22rc1, 6.4.7rc1, 7.0.0alpha4, 7.0 (plan)

Type: Problem report Priority: Trivial
Reporter: Peter M. Assignee: Aleksandr Iantsen
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Team: Team INT
Sprint: Sprint 103 (Aug 2023)
Story Points: 0.5

 Description   

PagerDuty - Rulesets and Event Rules will end-of-life in 2024. 

Steps to reproduce:

  1. In PagerDuty change Ruleset to Event Orchestration (EO)
  2. Create Rule in EO
  3. Send alert via integration

Result:
An incident is not resolved automatically if it falls within the rule. A message with the trigger action "Resolve" cannot be filtered using a rule, and PagerDuty cannot resolve the incident using dedup_key.

 

Example:

{     "dedup_key": "157510087",     "event_action": "resolve" }

This message not contains rules matches and cannot be resolved.

Expected:
Incident should be resolved if matched by rules



 Comments   
Comment by Peter M. [ 2023 Jul 21 ]

Fixed.

The following code has been added:

    else if (params.eventvalue == 0) {
        fields.event_action = 'resolve';
        fields.payload = {
            summary: params.eventname,
            source: (params.event_source === '1') ? 'Discovery' : params.hostname + ' : ' + params.hostip,
            severity: severityMapping[params.severity],
        };
        
        if (params.event_source === '0') {
            fields.payload.custom_details = {
                'Event date': params.eventdate,
                'Event time': params.eventtime,
                'Trigger description': params.triggerdesc,
                'Trigger opdata': params.triggeropdata,
                'Event tags': params.eventtags,
                'Event host': params.hostname,
                'Event host ip': params.hostip
            };
        }
    }

 

Comment by Aleksandr Iantsen [ 2023 Aug 24 ]

Implemented in:

Generated at Wed Mar 26 08:11:33 EET 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.