You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: umbraco-cloud/set-up/project-settings/hostname-monitoring.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,7 @@ Hostname monitoring can be accessed under **Insights > Hostname Monitoring** on
12
12
## Hostname Monitor Configuration
13
13
14
14
-**Hostname**: The domain or subdomain to monitor (e.g., `https://example.com` or `http://web.example.com`). Users can also monitor hostnames outside of Umbraco Cloud, such as static frontend websites hosted elsewhere for Heartcore projects.
15
-
-**Frequency**: The interval at which the hostname is checked (e.g., every X minutes). Valid values: 1, 5, 10, 15, 30, 60, 360, 720, 1440 minutes.
15
+
-**Frequency**: The interval at which the hostname is checked (e.g., every X minutes). Valid values: 5, 10, 15, 30, 60, 360, 720, 1440 minutes.
16
16
-**Locations**: Users can select multiple locations to ping the web application from. Supported regions include Europe, the US, Australia, and the UK.
17
17
-**Max Response Time**: The maximum acceptable response time in seconds. Must be greater than 0.
18
18
-**Expected Status Code**: The HTTP status code that indicates a successful response (e.g., `200`, `301`, `404`). Any status code can be monitored, and this value determines whether the UI marks the response as a failure or success.
@@ -31,7 +31,7 @@ Hostname monitoring can be accessed under **Insights > Hostname Monitoring** on
31
31
32
32
| Plan | Lowest Frequency | Max Locations | Historical Data | Hostnames Monitors Supported |
0 commit comments