Status Code for Webchecks

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

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. 

3 hours ago, azia said:

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. 

Yeah, that's not likely to change. Giving someone the ability to run their code on our point of presence on the internet, could have huge legal ramifications. Even when there is a trusting relationship involved.

2 hours ago, Stuart Weenig said:

Yeah, that's not likely to change. Giving someone the ability to run their code on our point of presence on the internet, could have huge legal ramifications. Even when there is a trusting relationship involved.

Doing the standard external webcheck is fine, and really all we need for this scenario, just that the the HTTP Status Code data isn't outputted and displayed.

We don't want to run custom code for this (not in our environment/s nor in LM point of presence), that is what we are trying to minimize. Unfortunately, due to the lack of HTTP Status Code output we are forced to do run custom code in an ever increasingly unmaintainable amount of datasources in VMs across our and customer environment.

Apologies for my previous words causing the misunderstanding about us wanting to run custom code on LM.

Gotcha. No problem. Mostly what I do here for feature requests is qualify the request. Now we'll see what the Product Management team says.

It would be good if anyone else who wants this chimed in about it.