Skip to main content

Multiple Uptime Monitors for a single Child site

Core Requests (Dashboard/Child)Administrative

Did a client ever call you to say their website was “down”, but Uptime Monitor didn’t detect it?The reason is often an agressive caching strategy where the homepage is full cached, but as soon as you try to log in the site, or use the cart on an e-commerce site, the experience breaks down.For this reason, I would like to have the ability to add multiple Uptime Monitors for a single site, so I could elect to monitor not only the homepage, but also the shop, the login page, to ensure over-agressive caching is not masking a problem with the rest of the site.Today, we can create multiple HTTP monitors, but only the one for the Homepage is showing up on a site’s dashboard screen in MainWP.In an ideal world, we would be able to associate additional Monitors to a given site, and they would all show up on that child’s dashboard in MainWP.Anyone interested… anyone? … anyone?

Posted by Imported from Legacy Board ·
Status: Completed2 comments

Log in to comment and vote

Comments2

  • Bojan Katusic

    Team•

    Aug 27

    Both parts of this request are now available.

    You can create Sub-Monitors for additional URLs/slugs, and MainWP Dashboard 6.1.8 now includes an optional Attempt to bypass page cache setting for uptime checks.

  • Benoit

    •

    Aug 17

    I’ve faced this problem so many times, and unfortunately it can seriously affect the relationship with clients.

    When a website goes down but MainWP still reports it as UP because a cached page keeps returning a 200 status code, the client is sometimes the one who notices the outage first.

    From their perspective, it makes the monitoring service look unreliable and can make me appear less professional.

    I really think MainWP needs a native solution for this, ideally a global option to monitor an uncached response or automatically bypass page cache during uptime checks.

    This is especially important for WooCommerce websites, where WordPress/PHP can be completely broken while the cached homepage still responds with HTTP 200.