I have raised this as a bug in the HTTP Loader and it was rejected there, yet, I have discussed this feature request with a Centreon support guys and he was keen on raising this again as a new feature, and not a bug.
Allow me to explain why this feature would be absolutely great in Centreon...
Many of my colleagues including myself have a server or NAS at home which is running uptime-kuma, and they have created a status page for DHL public internet services. These uptime kuma instances run locally, so we created a page to test from the source of every ISP in our part of the country…(from the principle: page of colleague A going down → ISP issue vs all pages showing issues → effective problem with our public services)
The enormous advantage of this tool is that is is freeware, largely deployed, available on all OSes and IOT devices and is not hosted in the cloud, hence you can really do checks per ISP.
I would like to display such a service overview (the “external” view into our applications) within Centreon, but we are receiving a connection refused error…
Other (PHP/HTML based) websites are displayed in the HTTP Loader correctly, but when I curl the UptimeKuma status page, no webpage body is displayed...I guess because the node.js parts are not rendered
I could easily build a similar view in Wordpress, but the monitoring plugins in wordpress are running somewhere on a cloud subscription (and not locally) and this is a disadvantage: I do not want to provide a list of my company hosts to a third-party, and the monitoring then relies on the uptime of a single cloud subscription which is basically blackbox
If Centreon could create something similar to the HTTP Loader, this would allow the addition of http(S) monitoring from public webservices, from the public perspective of various local ISPs, displaying it internally on the central monitoring solution