Hello,

we will put it onto the wishlist.

best regards.

Did some further testing on this.

The server I am sending to does not require Content-type set for JSON, so this should work as-is (but does not).

My notification has HTTP Action enabled with the following: URL: http://events.pagerduty.com/generic/2010-04-15/create_event.json Postdata: { "service_key": "ServiceKeyDeleted", "incident_key": "prtg/test", "event_type": "trigger", "description": "Test event without placeholders", "details": { "status": "status", "device": "device" } }

If I telnet to their server directly and post as below, it works.

----------------------Submit by telnet to events.pagerduty.com 80----------------------
POST /generic/2010-04-15/create_event.json HTTP/1.1
Host: events.pagerduty.com
Content-Length: 215

{ "service_key": "ServiceKeyDeleted", "incident_key": "prtg/test", "event_type": "trigger", "description": "Test event without placeholders", "details": {  "status": "status", "device": "device" } }

----------------------End----------------------

Can you shed any light on what else PRTG might be adding to the postdata? PRTG logs only show "HTTP/1.1 400 Bad Request" for a test notification. Any way I can get to the data being returned?

I think the problem is, that PRTG encodes the POSTDATA and that may break pagerduty's stuff. We will look into creating pagerduty support in one of the next versions.

Thanks for the update and for giving this some consideration.

Even a simple option to encode or not encode the postdata on an HTTP notification would be a convenient shorter-term solution.

It's also be helpful to have state change notification options for "Down Acknowledged" and "Paused" (this would let us do our acknowledgments in PRTG and then pass that notification out ).

Thanks again.