Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-75964

resolve incidents not working anymore

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Blocker Blocker
    • pagerduty-plugin
    • None
    • Jenkins version 2.346.3
      PagerDuty Plugin Version 0.7.1

      We're using the "PagerDuty Incident Trigger" post-build-action and have configured the following fields:

      • Routing Key
      • Dedup Key
      • Summary
      • Source
      • Severity
      • Component
      • Number of Consecutive builds before Triggering

      Triggers are set to: 

      Incident creation works fine as you can see in the following log: 

       

      Aug 04, 2025 1:18:15 PM FINE com.github.dikhan.pagerduty.client.events.HttpApiServiceImpl notifyEvent
      {"dedup_key":"MyDedupKey","message":"Event processed","status":"success"}
      Aug 04, 2025 1:18:15 PM FINE com.github.dikhan.pagerduty.client.events.PagerDutyEventsClient sendEvent
      Event result EventResult{status='success', message='Event processed', dedupKey='MyDedupKey', errors='null'} for Incident { routingKey='xxx', eventAction=trigger, dedupKey='MyDedupKey', payload=Payload { summary=MySummary, source=MySource, severity=critical, timestamp=null, component=Jenkins, group=, eventClass=, custom_details=null }, images=null, links=null } 

       

      Following log shows what the plugin is sending as resolve message:

       

      Aug 04, 2025 1:18:52 PM FINE com.github.dikhan.pagerduty.client.events.HttpApiServiceImpl notifyEvent
      {"dedup_key":"MyDedupKey","message":"Event processed","status":"success"}
      Aug 04, 2025 1:18:52 PM FINE com.github.dikhan.pagerduty.client.events.PagerDutyEventsClient sendEvent
      Event result EventResult{status='success', message='Event processed', dedupKey='MyDedupKey', errors='null'} for Incident { routingKey='xxx', eventAction=resolve, dedupKey='MyDedupKey', payload=Payload { summary=BLANK, source=BLANK, severity=info, timestamp=null, component=null, group=null, eventClass=null, custom_details=null }, images=null, links=null } 

      It seems like the plugin does not send all required fields to resolve an incident: https://developer.pagerduty.com/api-reference/368ae3d938c9e-send-an-event-to-pager-duty

       

      If we manually post the following with curl the incident will be resolved on PagerDuty side: 

       

      curl --request POST \
        --url https://events.pagerduty.com/v2/enqueue \
        --header 'Accept: application/json' \
        --header 'Content-Type: application/json' \
        --data '{
        "payload": {
          "summary": "MySummary",
          "source": "MySource",
          "severity": "info"
        },
        "routing_key": "xxx",
        "dedup_key": "MyDedupKey",
        "event_action": "resolve"
      }' 

      Can you please add the required fields to the payload for the resolve message?

       

            alexanderlz Alexander Leibzon
            bdude Bernd
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: