Advanced Monitoring Update: Faster Overviews, Smarter Controls, And More

Monitoring one client site is simple. Monitoring fifty is not.

Every site needs a different level of attention, so agencies add tools as new needs come up. Soon, alerts are spread across dashboards, inboxes, and spreadsheets. One screen says a site is fine while another has a warning buried three tabs away.

That is how things slip through the cracks. And sometimes, the first useful alert is still the client asking, “How long has this been broken?”

The hard part is not getting more alerts. It is knowing which site needs attention and where to look next.

That is what Advanced Monitoring in WP Remote brings into one place.

Choose the monitoring that makes sense for each site. Every check feeds the same portfolio overview, where you can see what is healthy, what needs attention, and what is critical. Open a group, choose the affected site, and move straight into the details.

One dashboard. A few seconds to understand the portfolio. Two clicks from “something is wrong” to the context your team needs to start fixing it.

One Dashboard for the First Five Minutes

Most agency mornings start with the same question: Is anything broken?

Until now, answering that meant opening sites one by one. The Dashboard Overview could show you the portfolio, but it could not quickly tell you which monitoring issues needed attention first.

The new Advanced Monitoring widget puts that answer on the first screen. Every monitored site falls into one of four groups:

• Critical: a problem needs attention now.
• Warning: something needs checking before it becomes urgent.
• Healthy: monitoring is active, and no issue has been found.
• Disabled: monitoring is turned off for that site.

Critical issues are shown ahead of warnings. A site that is down does not get buried below a certificate that will expire later. And a site is not marked Healthy just because one check passed while another failed.

The Critical group covers problems such as downtime, failed visual checks, missing page content, a domain or SSL certificate that has expired or will expire within 24 hours, PHP fatal errors, and failed form monitors. Warning catches issues that need attention soon, including upcoming domain or SSL expiry and PHP warnings. The summary does the sorting before your team starts clicking.

Below the summary, Recent Issues shows the problems currently affecting monitored sites. Domain and SSL warnings include the number of days remaining, so the team can judge how soon to act. Filter the list by monitor type when you are working through a specific queue, or leave it unfiltered for a quick check across the portfolio.

That gives the team a simple starting point. Check Critical. Review Warning. Move on when the rest of the portfolio is Healthy.

No tab hunt. No opening fifty sites to find the one that needs you.

Scan the Whole Portfolio by Monitor Type

The overview tells you there is a problem. The global monitoring pages show you where it is.

Say the dashboard shows an uptime issue. Open the Uptime Monitoring list, and you can compare every client site in one view: current status, check frequency, last check, and the last 24 hours of uptime. Down, Unknown, and Disabled sites stand out without a site-by-site search.

That list also gives you a direct route into each site’s details. The portfolio view answers “which sites?” first; the site view answers “what happened?” only when you need it. You can scan the portfolio quickly and open the full details only for sites that need work.

The Domain Monitoring list does the same job for domains. You can see each domain’s status, expiry date, and registrar together, then search or filter the list when you need to narrow it down.

Page Content Monitoring shows which pages are being watched, which checks found an issue, and which words are missing. You can review changes across the portfolio without visiting every page yourself.

These lists are useful when work is divided across a team. One person can handle uptime issues while another reviews upcoming domain expiries. Everyone works from the same current view, and no one has to maintain a separate spreadsheet just to keep the queue straight.

See What Happened When a Site Goes Down

When an uptime warning appears, “the site is down” is only the start. Your team still needs to know when it began, whether the problem is still happening, and which region saw it.

Open the site’s Uptime page, and those answers are together. The summary shows the current status, how often the site is checked, when it was checked last, and how many incidents were recorded. The 24-hour timeline shows when checks passed or failed, while the world view breaks the result down by region. You can also enable or disable the monitor from this page.

If the site is healthy again, you can confirm the recovery without searching through a general activity log. If it is still down, the current incident and affected region are visible on the same page.

In the example below, the site is currently down. The page shows one ongoing incident, an 801 status from the monitor, and a failed check from Europe. Your team can see the current state before opening any deeper records.

Need the individual checks? Open Probe History. Each row shows when the check ran, the returned status code, the monitor state, the region, and the probe IP. Filters help you focus on a time range, region, status code, or error.

The page shows current incidents and check history; it does not create a full incident report. But it gives the person handling the issue the facts they need right away: when checks started failing, where they failed, and what the monitor returned.

That is a much better client update than “we got a downtime alert.” It is also a much better handoff to the developer or host who needs to investigate.

Stop Tracking SSL and Domain Dates from Memory

SSL certificates and domains usually give you time before they expire. The problem is noticing the warning while there is still time to act.

That gets harder when different clients use different registrars, renew on different dates, and hand account access to different people. A date in someone’s calendar is easy to miss. A warning in the same monitoring view as the rest of the portfolio is much harder to lose.

SSL Monitoring keeps the current certificate status, expiry date, and validation result together. Open a site to see the certificate details and chain, then use Probe History to check what WP Remote recorded over time.

The detail matters when a certificate is marked Invalid. You can check whether the common name matches, whether the certificate chain is complete, and whether the revocation check passed. Probe History keeps those results with the check time and expiry date and lets you filter by validation or revocation status. The team sees what needs checking instead of being left with a generic SSL warning.

Domain Monitoring brings the same visibility to domain expiry. The global list shows which domains are Healthy, Unknown, or Disabled, along with expiry dates and registrars. Open a site to see the registration date, nameservers, last check, next check, and the number of days left before expiry. You can refresh the details or turn monitoring on and off from the same page.

WP Remote does not renew a domain or replace a certificate for you. It makes the next deadline and the current status visible before either becomes an emergency. The team can see which client needs a reminder, which account needs checking, and which task should be assigned today.

Catch Problems That Uptime Checks Cannot See

A green uptime check only tells you that the page responded. It cannot tell you whether a contact form still works or whether an important line of copy was removed.

Those problems are easy for an agency to miss. The site looks fine at a glance. The client notices only after enquiries slow down or someone spots the wrong content on a live page.

Form Monitoring keeps each monitored form in one list with its name, form type, page URL, check interval, current status, and available actions. Add a monitor for the forms that matter, then review their status alongside the other checks for that site. A contact form can have a different check interval from another form, without sending the team to a separate monitoring tool.

Page Content Monitoring watches for words that should remain on important pages. The overview shows which pages are being checked, how often they are checked, and where a word is missing. It also shows how many pages need review, without making the team open them one by one.

Open a page to see its Baseline History. The history shows which words were present or missing at each check. If the change was intentional, Update Baseline accepts the current version as the new point of comparison.

If a pricing line or required notice changes unexpectedly, you can see when it first went missing. If the client approved the new copy, update the baseline. Either way, the team catches the change without adding another round of manual page checks.

Monitoring Finds the Problem. Your Team Fixes It.

Advanced Monitoring does not bring a site back online, renew a domain, replace a certificate, or rewrite a page. Your team still owns the fix.

The time saving comes before the fix. The right person can see the warning, open the affected site, and review the latest status without reconstructing the issue across several tools. By the time the task is assigned, the team already knows what failed and where to start.

That saves time during the part of an incident that is usually the messiest: confirming the problem, finding the right evidence, and deciding who should take it.

From Monitoring Noise to Portfolio Control

At agency scale, monitoring should not mean more dashboards to check. It should mean one place to see what needs attention.

Choose the checks that fit each client site. Let them all feed the same overview. Start with Critical and Warning, open the relevant list, and move into the site details when you need them.

Your team spends less time looking for the problem and more time dealing with it. And more often, you are the one telling the client an issue is already being handled, not the other way around.