1. Home
  2. Technical info

Technical info

1. Data storage

When every check is executed, we store a large amount of data. This data is used to populate the many detailed reports in Alertdesk and for troubleshooting.

1.1. What do we store

The data we store depends on the type and state of the check.

Uptime Check UP

  • All request data like host, protocol, headers, etc.

Uptime Check DOWN or FLAPPING

  • All request data like host, protocol, headers, etc.
  • Response Headers
  • Response Body (first 64kB uncompressed)

On assertions validating we use the full uncompressed Response Body. But we only store the first 64kB uncompressed.

1.2. Data retention

We store the check result data according to the following retention policy:

  • 1 minute is saved for 24 hours
  • 30 minutes is saved for 1 month
  • 1 hour is saved for 90 days (3 months)
  • 2 hours is saved for 180 days (6 months)
  • 1 day is saved for 1095 days (3 years)
  • 1 week is saved for 1825 days (5 years)
  • 1 month is saved forever

We are continuosly working on uptimization of the platform. Expect updates to our retention policy.

2. Check data truncation

Uptime Check truncates the response when 64 kilobytes have been read from the target host. This means assertion data must be placed within the first 64 kilobytes of data if the page response body exceeds this data limit.

3. Whitelist

All checks are executed from different locations in Amazon Web Services (AWS) cloud service. If you need to whitelist the traffic from Alertdesk in your firewalls, external caching services, and so on.

On every check, we, by default, add a default HEADER to the HTTP request.

User-Agent = Alertdesk/version

You can use this default User-Agent to whitelist the traffic from Alertdesk.

As the version number will change over time, you should only verify that the User-Agent contains the String Alertdesk.

3.1.1. Use a secret header

As our default user-agent is public for everyone, we recommend you to add your own HTTP header and use this for whitelisting.

Example with own header

3.1.2. Cloudflare

If you are using Cloudflare in front of your website, we recommend that you whitelist the traffic from Alertdesk, to avoid our check runner to get blocked.

Follow this step-by-step-guide to whitelist the Alertdesk User-Agent.

1. Choose website
Click on the website, where you wish to allow Alertdesk User-Agent.

Click on the website, where you wish to allow Alertdesk User-Agent
2. Firewall settings
Click on the firewall icon.

Click on the Firewall icon
3. Firewall Rules
1. Click on Firewall Rules in the submenu
2. Click the button Create a Firewall rule

Click on Firewall Rules
4. Create new firewall rule
1. Give your new rule a name
2. Select User Agent in the Field dropdown
3. Select Contains in the Operator dropdown
4. In the Value field enter Alertdesk
5. Select Allow in the Action drowdown
6. Finally, click on the Deploy button to confirm

Follow the instructions to add a new rule
5. Whitelisting enabled
The new firewall rule is now enabled.

Your new firewall rule is created

3.1.3. Fastly

If you are using Fastly as caching-node infront of your website, we recommend you to whitelist our useragent, so the request goes directly to the webservers to insure we don’t get a cached result from Fastly.

1: Login to Fastly.com and go to “Configure”
first go to https://www.fastly.com/ and login to your account.
The click on “CONFIGURE” in the top menu.
Important: If you have multiple domains then select the right domain by clicking on “Switch Services”
2: Edit Configuration
Click on “EDIT CONFIGURATION” and then “Clone version XX (active) to edit”
3: Settings
Click on “Request settings” under “Settings” in the left menu.
4: Request settings
5: Create a request setting
Type in Name: Alertdesk Agent
In Action select “Pass (do not cache)”
Then click on “attach a condition” in the top, which will open a new window.
6: Add a condition
7: New request condition
Type in Name: Alertdesk Useragent
Type in Apply if…: req.http.User-Agent ~ "(?i)Alertdesk\/.*"
So it looks like below image.

8: Request setting
You are now back to the previous window. Here you must make sure it looks like the image below.
Then click “CREATE”
9: Activate new configuration
You are now ready to activate the new configuration.
Click on the greenish button “ACTIVATE” at the top.

Configuration is now ACTIVE

3.2. IP-address

Because we use AWS to host our platform, you need to whitelist the public list of IP-ranges from AWS:

See the full updated public list of AWS IP-ranges here

Maintaining these IP-ranges is a significant task as AWS is continuously updating them.

At the moment we don’t offer a static IP-range, but we recommend you to use HTTP headers for whitelisting.

3.3 Google Analytics

Follow this guide to exclude Alertdesk traffic, if you see misinformation in your Analytics data caused by our services

Our Uptime-check doesn’t affect Analytics data.

First, you must add the following UTM source tag to your check(s): ?utm_source=alertdesk
To do this then edit your Speed check in the Alertdesk dashboard
So it looks like this example:

Then go to your Google Analytics account
1: Click on the admin icon
2: Select “All Filters”
3: Click on “+ ADD FILTER”

1: Enter name for the filter (ex. Alertdesk monitoring)
2: Select “Custom”
3. Select “Campagin Source”
4: Enter alertdesk
5: Select which View to apply filter to
6: Click on “Add”
7: Click “Save” and filter is now applied

Updated on February 25, 2021