New Feature: Concurrent Monitoring

We’ve added a new feature to your monitoring settings, Concurrent Monitoring. Now you can choose to have Uptrends test from multiple locations at the exact same time. Not only will you have more data for your analysis, but you also get your alerts quicker leading to faster problem resolution.

What is Concurrent Monitoring?

When you enable Concurrent Monitoring for an Uptrends monitor, you choose three or more checkpoint locations from Uptrends’ 220+ checkpoints. Instead of testing from only one checkpoint at a time, your monitor check happens on all your chosen checkpoints simultaneously. If you’ve chosen five checkpoints and set your test interval to one minute, your monitor makes 300 tests an hour.

What are the advantages of Concurrent Monitoring?

The main advantages of concurrent monitoring are more data and faster error detection.

Concurrent Monitoring = more data

As illustrated earlier, a single uptime monitor with five checkpoints can generate 300 tests per hour. A standard monitor (a single checkpoint monitor) can generate at most 60 checks an hour.

If the metric you’re tracking is for performance, you get a much better view of your performance with 60 tests vs. 12. More data simply means better data. You have a more complete view into your web assets.

Concurrent Monitoring = faster alerting

When your standard monitor encounters an error, Uptrends records the error as unconfirmed. To confirm the error, Uptrends schedules the test again immediately. If the monitor gets a second error, Uptrends records the error as confirmed and issues an alert. Depending on the monitor type, the elapsed time from unconfirmed to confirmed can take a minute or more (some transaction monitors take nearly four minutes to complete). If the problem is intermittent or localized, a second test may succeed. You see the unconfirmed errors in your reporting, but no alerts go out. Concurrent Monitoring fixes that.

When you set up your concurrent monitoring, Uptrends defines confirmed and unconfirmed errors as the percentage of errors returned. For example, your monitor uses five checkpoints, and you have your alert level set to 25% failure rate. On any given check, if one check fails, Uptrends records an unconfirmed error and follows up with another test. If two checks fail, the monitor surpasses the 25% rate, and an alert goes out immediately. Using the error thresholds allows you to detect intermittent and localized errors quicker without unwanted alerts.

Concurrent Monitoring alerting thresholds

Can I pick from all the checkpoints?

Your checkpoint selection options depend on the number of checkpoints you choose. If you choose only three checkpoints, you’re limited to what’s called “High Availability” checkpoints (more on that in a moment). If you opt to use a minimum of 5 checkpoints, you may choose from any of Uptrends checkpoints for your concurrent monitoring.Concurrent Monitoring checkpoint selection

What does high availability mean?

High availability checkpoints are simply Uptrends checkpoint locations that have two or more servers. For example, our New York checkpoint has two servers working behind the scenes conducting the monitoring checks. During checkpoint maintenance, we have to take servers offline for a short period. If a checkpoint has only a single server, the checkpoint is not available to conduct your testing during maintenance. When you select high availability checkpoints, the servers don’t all come down at once, so the checkpoint continues to conduct tests, and your monitoring continues without interruption.

How does Concurrent Monitoring look in my reports?

We’ve made several changes in your logs and Check Details reports to accommodate Concurrent Monitoring.

Monitor Logs

Your Concurrent Monitoring checks appear in your monitor logs alongside your standard monitoring checks. Your concurrent checks appear with a four-dot icon before the name. The check with the four black dots is representative of the entire group of checks (called the overall check) showing averaged data based on the different checks conducted concurrently (see figure below).

Note: Waterfall data is not aggregated and averaged in the overall Check Details report.

Monitor log

You can include the contributing individual checks in your logs as well.

  1. Click the gear icon at the top-right corner of the monitor log tile.
  2. Check the Show partial measurements box on the Tile tab.
  3. Click Set (see figure below).

The individual checks that comprise the monitor now show in your monitor log. They also include the four-dot icon, but they only have one solid black dot (see figure below).

Concurrent Monitor Dashboard

From your monitor logs, you can access the dashboard for a particular monitor by hovering over the monitor’s name and selecting Dashboard from the fly-out options (see figure below).

Accessing a monitor dashboard from the Monitor LogWe’ve developed a default dashboard that includes the Multicheckpoint Chart tile. The chart includes your data for each checkpoint over time. The figure below shows the total time for a span of about three hours for five checkpoints. The tile can display up to ten checkpoints. Likewise, the Multicheckpoint List title gives you your metrics on a per-checkpoint basis.Multicheckpoint chart tile

Check Details

When you click the date for a Concurrent Monitoring check in your monitor logs, you get the Check Details report for that instance of the check. If you click the overall check (four black dot icon), you see the averaged details and the results per check. In the uptime monitor check shown below, you can see each result in the Concurrent checks section.

Concurrent Monitoring top level Check Detail report

Clicking on the checkpoint name in the Concurrent checks section brings up a detailed view of that specific check (see figure below). You can use the View all checks link under Concurrent checks (see figure below) to return to the overall report.

Concurrent Monitoring individual Check Detail report

Is Concurrent Monitoring supported in the Uptrends API

Absolutely. We’ve added new fields to your Monitor API and the MonitorCheck API. Check the API documentation to review the new API additions for Concurrent Monitoring.

How much does Concurrent Monitoring cost?

We’ve based the cost of Concurrent Monitoring on the type of monitor and the number of checkpoints selected. So, if you have a transaction monitor that uses three transaction credits, and you want it to run on five checkpoints, the new concurrent monitor uses 15 transaction credits.


  • One HTTPS uptime monitor uses one monitor credit for a standard monitor. When you switch the monitor to concurrent with five checkpoints, the new concurrent monitor uses five monitoring credits.
  • One Full Page Check monitor uses one browser monitor credit for a standard monitor. Switching that same monitor to concurrent with five checkpoints, the monitor uses five browser monitor credits.
  • One transaction monitor uses five transaction credits as a standard monitor. As a concurrent monitor with three checkpoints, the monitor uses 15 transaction credits.
  • One Multi-Step API monitor has three steps and uses three API monitor credits as a standard monitor. As a concurrent monitor with six checkpoints, the monitor uses 18 API monitor credits.

How do I get Concurrent Monitoring?

Concurrent Monitoring is now in paid public beta, and available to Business and Enterprise plans. If you would like to participate, please review our Concurrent Monitoring Beta program documentation. Concurrent Monitoring is available to you now in your account.

What do you mean by public beta?

Our developers worked for a long time to develop and test Concurrent Monitoring before moving to the private beta. In private beta, we worked with some of our customers to further refine the new feature. At this point, the new feature has had months of testing, and we consider it stable and reliable. The public beta is the final test of the usability of the product. The public beta helps to make sure that you get the value you expect from your Uptrends monitoring.

Advantages of participating in the public beta

Besides being an early adopter, you get your input heard. The developers continue to refine the product during the beta process. Feedback from the beta participants frequently makes it into the product. This is your chance to make a difference in the product you would like to use anyway. Go ahead, open that support ticket. Although our developers can’t respond to every suggestion or request, our developers do discuss your ideas at their design meetings.

Want to learn more?

Your monitoring consultant can help you out with any additional questions you may have. Or you can schedule a demo for a one-on-one virtual meeting. We have a Knowledge Base article to help you out, and our Support team is always ready to answer your questions too. We are eager to get your feedback. Start using Concurrent Monitoring Beta today!