MQ

One option you can use the `api/docs` route to ensure the webserver is available.

https://abc.ibm.com/api/docs -> 200 ensures the webserver is available.

If you want to ensure the webserver is authenticating etc.. add credential to the endpoint - https://abc.ibm.com/ibm/api/explorer/

That is a bummer then, but as expected, we have to create our own type of heartbeat to monitor the webserver.

By “monitor” I presume you mean “determine if the (insert resource here) is available and ready to successfully perform workload at a precise point in time.”  

There is no simple answer, other than attempting the intended workload.  It either works, or it doesn’t.  Cost-benefit analysis will dictate HA and DR efforts to mitigate failures.  

The same question has been discussed in other contexts, including queue manager, channel, data base manager, specific application, and other resources. 

Hey Bruce,

correct, in this particular case all that's needed is a heartbeat to see if the service is available.

While the discussion isn't new, apparently the webserver still is. We monitor all the MQ related resources with vendor monitors, but none of the ones we use have any option to check if the REST API is up or not, hence the question if there is something available.

I already made a dummy curl call and will pipe the output into a file to then postprocess the results.