Status Code for Webchecks

On 12/8/2020 at 5:22 PM, Stuart Weenig said:

Assuming you mean to have the actual status code and not the simplified version we show in the overallStatus datapoint, right?

That is correct. What we need is HTTP Status Codes. 

Again, we make our own Datasources for each Customer Website or API Endpoint, but that tends to get tedious, and harder and harder to maintain, because we have HUNDREDS of them, each with their own Polling, Timeout, and request Body customizations.

Another major limitation is that we can't use the External Webcheck Source, and are forced to limit the calls from the collectors in our Customer's environment, or keep spinning up VM resources on our end just to have AT LEAST ONE external sourced Webcheck.