ITRS named a Visionary in the 2024 Gartner® Magic Quadrant™ for Digital Experience Monitoring

Configuring error conditions is the first step in setting up your alerts. The error conditions define the conditions in which an alert is created and (if configured) an alert message is sent.

If you want to know more about how errors and alerts work together, check out the knowledge base article Alerting overview which contains the complete flow from monitor checks to alert messages.

What is an error condition?

An error condition lets you define what you regard as a noteworthy problem (an error) of your website, web service, or server. For example, depending on what your website needs to load (content, plugins, scripts) to be ready for the visitor, it may be up and running very quickly or take a bit longer. Only you can define what is good or acceptable for your website. That is why you have to decide on which errors you want to trigger and what the thresholds or specific conditions are.

In the Uptrends app error conditions are part of the monitor settings, on their own tab:

screenshot error conditions monitor setup

Different monitor types have different sets of error conditions, based on the monitor’s purpose and which data they collect.

Which error conditions are available?

The table below shows all error conditions grouped by category and for which monitor types they are available. The monitor type Full Page Check is mentioned by its acronym “FPC” here.

Please consult the knowledge base articles that are linked in the table below for detailed information on how the individual error conditions work.

Note that a Multi-step API monitor (MSA monitor) uses a different way to detect errors. It has no error conditions as described here.

Category Error condition(s) Available for monitor type
Availability General availability All*
Availability HTTP status code match HTTP(S), Webservice HTTP(S)
Page content Page content match HTTP(S), Webservice HTTP(S), FPC
Element URLs Check if any URL in the list of resources matches a (RegEx) value FPC (browser type “Chrome with extra metrics”), Transaction (within steps)
Element URLs Check if none of the URLs in the list of resources matches a (RegEx) value FPC (browser type “Chrome with extra metrics”), Transaction (within steps)
Load / Running time Concern level threshold All*
Load / Running time Critical level threshold All*
Core Web Vitals Use recommended Core Web Vitals FPC (browser type “Chrome with extra metrics”), Transaction (within steps)
Core Web Vitals Maximum time to First Contentful Paint FPC (browser type “Chrome with extra metrics”), Transaction (within steps)
Core Web Vitals Maximum time to Largest Contentful Paint FPC (browser type “Chrome with extra metrics”), Transaction (within steps)
Core Web Vitals Maximum Time To Interactive FPC (browser type “Chrome with extra metrics”), Transaction (within steps)
Core Web Vitals Maximum Total Blocking Time FPC (browser type “Chrome with extra metrics”), Transaction (within steps)
Core Web Vitals Maximum cumulative layout shift score FPC (browser type “Chrome with extra metrics”), Transaction (within steps)
W3C metrics Request start FPC (browser type “Chrome with extra metrics”), Transaction (within steps)
W3C metrics Time to first byte FPC (browser type “Chrome with extra metrics”), Transaction (within steps)
W3C metrics DOM interactive FPC (browser type “Chrome with extra metrics”), Transaction (within steps)
W3C metrics DOM completed FPC (browser type “Chrome with extra metrics”), Transaction (within steps)
Console content Console log message content check FPC (browser type “Chrome with extra metrics”), Transaction (within steps)
Resources Sum of all resources minimum / Content FPC, HTTP(S), Webservice HTTP(S), Transaction (within steps)
Resources Sum of all resources maximum FPC, Transaction (within steps)
Resources Percentage of elements fail to load FPC, Transaction (within steps)
Resources Percentage of elements over certain size FPC, Transaction (within steps)

*HTTP(S), FPC, Transaction, Webservice HTTPS, DNS, SSL, (S)FTP, SMTP, POP3, IMAP, MS SQL Server, MySQL, Ping, Connect

How to configure an error condition

Configuring an error condition can be done when building a monitor from scratch or by editing a monitor after it has already been added. If you need to add a new monitor, please check out the info in Adding monitors and add a new monitor first.

To configure error conditions:

  1. Go to Monitoring > Monitor setup.
  2. In the Monitors overview select the monitor you wish to add an error condition to.
  3. Open the Error conditions tab.
  4. Expand the error condition category that you want to configure by clicking the arrow in front of the category.
  5. Configure your error conditions as needed. For some categories you have to click the + New check button to start adding a condition.
  6. Repeat adding and configuring conditions for other categories.
  7. Once you are done, click the Save button to save all your changes.

All articles in this category

By using the Uptrends website, you consent to the use of cookies in accordance with our Cookie Policy.