Revert to Pingdom Standard Http Check

[stefan-guggisberg]

Is your feature request related to a problem? Please describe.
The Pingdom Http Custom checks that we’re currently using are IMO useless for Root Cause Analysis & Troubleshouting . Only the Status and the Response Time of the XML response are processed/reported on Pingdom.com. The additional information/context that helix-pingdom-status provides (such as <activation> and <error>) is ignored by Pingdom and doesn’t show up on Get Content. Neither do the received headers. As a consequence you’ll have to manually dig through the activations to find the action response.

Describe the solution you'd like
Reverting back to standard Http check support all information (status code, response body, response headers) is available on Get Content. For simplicity's sake I suggest we keep the current XML response format but return an appropriate Http error status in case of an error (instead of unconditional 200 as mandated by the custom Http checks). Returning a status != 200 will trigger an incident. We'll have to reconfigure the Pingdom checks.

[adobe-bot]

🎉 This issue has been resolved in version 3.0.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀