SW Custom Properties in PagerDuty alerts

bourlis

I'm in the process of testing PagerDuty's integration with Solarwinds.  We want to push some custom properties through the API calls to assist in PagerDuty call routing, on-call staffing and special call out features that we currently have in our alarming.  The custom propterties I have are responsible team, primary contact, on call, alt contact & disposition.

I'm new to  API's so I don't really know where to search and what I'm doing, so I figured what better place to go then Thwack. Here's what the the default API looks like:

{

"service_key": "${SQL: SELECT Nodes.PDIntegrationKey FROM Nodes WHERE NodeID='${NodeID}'}",

"incident_key": "${NodeName} ${N=SwisEntity;M=Status}",

"event_type": "trigger",

"description": "Alert: ${NodeName} is ${Status}",

"client": "SolarWinds",

"client_url": "${N=SwisEntity;M=DetailsUrl}",

"contexts": [

{

"type": "link",

"href": "${N=Alerting;M=AcknowledgeLink}",

"text": "Acknowledge in SolarWinds (Does not ack in PagerDuty)"

}

]

}

Here's what what I added that's not working, but hopefully you can see what I'm trying to do:

{

"service_key": "${SQL: SELECT Nodes.PDIntegrationKey FROM Nodes WHERE NodeID='${NodeID}'}",

"incident_key": "${NodeName} ${N=SwisEntity;M=Status}",

"event_type": "trigger",

"description": "Alert: ${NodeName} is ${Status}",

"client": "SolarWinds",

"client_url": "${N=SwisEntity;M=DetailsUrl}",

"details": {

"Responsible Team": "${N=SwisEntity;M=CustomProperties.ITD_Responsible_Team}",

"Primary Contact": "${N=SwisEntity;M=CustomProperties._Primary_Contact}:,

"On Call": "${N=SwisEntity;M=CustomProperties._Node_OnCall}",

"Alt Contact": "${N=SwisEntity;M=CustomProperties._Node_Alt_Contact}",

"Disposition": "${N=SwisEntity;M=CustomProperties._Disposition}",

}

         "contexts": [

{

"type": "link",

"href": "${N=Alerting;M=AcknowledgeLink}",

"text": "Acknowledge in SolarWinds (Does not ack in PagerDuty)"

}

]

}

Any idea on what I'm doing wrong or pointers to make this work would be greatly appreciated.

bourlis

A couple of things have changed with I first posted this.

PagerDuty changed their alarming format from a JSON API to a HTTPS Post, which resolved a couple of different issues for us.

But here's the HTTPS Post for node down that works. Custom properties and called out in the custom_details section.  

{

  "payload": {

    "summary": "High CPU load on ${N=SwisEntity;M=DisplayName}.",

    "source": "${N=SwisEntity;M=Caption}",

    "severity": "critical",

    "component": "${N=SwisEntity;M=MachineType}",

    "custom_details": {

        "Alert Definition": "${N=Alerting;M=AlertDescription}", "Responsible Team": "${N=SwisEntity;M=CustomProperties.ITD_Responsible_Team}",

        "CPU Load": "${N=SwisEntity;M=Stats.CPULoad},

        "Machine Type": "${N=SwisEntity;M=MachineType}",

        "Notification Profile": "${N=SwisEntity;M=CustomProperties.Notification_Profile}"

      }

  },

"routing_key": "${SQL: SELECT Nodes.PDIntegrationKey FROM Nodes WHERE NodeID='${NodeID}'}", 

"dedup_key": "${N=SwisEntity;M=Caption;F=OriginalValue}_${N=SwisEntity;M=Caption}_${N=SwisEntity;M=MachineType}", 

"event_action": "trigger",

}

The nice thing about this is we have a very detailed and elaborate custom property section.  We can now simplify alerting in Solarwinds, supply all the different custom properties and then build superior notification filters and rules in PagerDuty.