Creating a monitorCopy Anchor Link

General SettingsCopy Anchor Link

Under Monitors → Create Monitor you will find the following mask:

First, give the new monitor a name and link the service you want to monitor. Next, define what the monitor should check. We offer preset option, but you can customize your monitor to your needs. Check out Advanced Settings for a fully tailored monitoring experience! Lastly, give your monitor an URL to keep tags on.

Advanced SettingsCopy Anchor Link

For HTTP monitors, the following methods can be chosen:

• GET: Retrieves the URI (Uniform Resource Identifier) of the target
• POST: Sends data to a server to create a new resource or perform an action.
• PUT: Updates the target or creates content within it
• DELETE: Removes the target
• PATCH: Makes partial changes to the target
• HEAD: Unlike GET, retrieves only the headers of the target; the body is not included
• OPTIONS: Returns the available HTTP methods and other options for the target to determine its capabilities

Under Regions, you can choose up to three locations to monitor your target independently. Additionally, you choose the amount of regions that have to fail in order to trigger an alert:

• all regions: Every region has to be down before an alert is triggered.
• a majority of regions: More than half of the regions have to fail.
• any region: One region is enough to trigger an alert.

Adding Valid Status Codes, Keywords and Headers is optional. You can change any parameter of your monitor under Monitor → Settings:

Monitor OverviewCopy Anchor Link

This is what your monitor overview looks like:

You can narrow down the timeframe of your data by scrolling while hovering over the graph. Scroll down to find failures, live checks of any region and related alerts. By clicking on any region card you will find the HTTP phase breakdown:

Here's what they stand for:

• Resolve measures the time required for a DNS resolution.

  → indication for the DNS resolution performance

• Connect is the time it takes to build a TCP connection after a DNS resolution.

  → indicates network latency and the server’s ability to accept connections

• TLS Handshake defines the required time for the negotiation and establishment of a secure SSL/TLS client-server connection.

  → shows the overhead of setting up encryption

• Time to first byte is the total time from request initiation to the first byte of response.

  → helps in assessing the server's responsiveness

• Transfer marks the time it takes from the first byte of the response to receiving the full response.

  → measures the download speed of the content from the server after the connection has been established