Skip to content

Umbraco Cloud - Hostname monitoring #6896

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 6 commits into from
Jun 4, 2025
Merged

Umbraco Cloud - Hostname monitoring #6896

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
7ea9f4a
hostname monitoring
pijemcolu Feb 18, 2025
8a0b565
Ignoring acronyms and other in error code table
sofietoft Feb 19, 2025
6c12000
Apply suggestions from code review
pijemcolu Mar 4, 2025
76ef235
Add a note about platform events
pijemcolu Jun 2, 2025
658839f
Fix vale markdown
sofietoft Jun 4, 2025
3105da3
Trigger gitbook checks
sofietoft Jun 4, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions umbraco-cloud/SUMMARY.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -54,6 +54,7 @@
* [Usage](set-up/project-settings/usage/README.md)
* [Bandwidth](set-up/project-settings/usage/bandwidth.md)
* [Availability and Performance](set-up/project-settings/availability-performance.md)
* [Hostname Monitoring](set-up/project-settings/hostname-monitoring.md)
* [Team Members](set-up/project-settings/team-members/README.md)
* [Technical Contact](set-up/project-settings/team-members/technical-contact.md)
* [Secrets Management](set-up/project-settings/secrets-management.md)
Expand Down
112 changes: 112 additions & 0 deletions umbraco-cloud/set-up/project-settings/hostname-monitoring.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,112 @@
---
description: >
A Hostname monitoring is a feature that allows users to track the availability and response times of their websites.
---

# Hostname Monitoring

Hostname monitoring in Umbraco Cloud allows users to track the availability and response times of their websites. This feature helps ensure optimal website performance and alerts users to potential downtime or performance issues. Users can add, edit, and view hostname monitors through the Umbraco Cloud Portal. A historical overview of uptime is available in the **Ping Results** section.

Hostname monitoring can be accessed under **Insights > Hostname Monitoring** on your project in the Umbraco Cloud Portal.

## Hostname Monitor Configuration

- **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.
- **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.
- **Locations**: Users can select multiple locations to ping the web application from. Supported regions include Europe, the US, Australia, and the UK.
- **Max Response Time**: The maximum acceptable response time in seconds. Must be greater than 0.
- **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.
- **Monitor Enabled**: Toggle to enable or disable monitoring. Disabling a monitor stops the pings but retains history in **Ping Results**.

## Ping Results

- Displays logs of pings, including:
- Timestamp
- Duration
- Monitoring server location
- Response code
- A response code different from `200` may indicate an issue.

{% hint style="info" %}
The Ping Results table also shows [platform and CMS events](./availability-performance.md#platform-and-cms-events), making it possible to see how different events impact performance.
{% endhint %}

## Plan Limitations

| Plan | Lowest Frequency | Max Locations | Historical Data | Hostnames Monitors Supported |
|---------|------------------|---------------|-----------------|------------------------------|
| Starter | 15 minutes | 1 | 1 month | 1 |
| Standard| 10 minutes | 2 | 3 months | 5 |
| Pro | 5 minutes | All | 12 months | 20 |

## Notes

- A Ping Result response code of `-7` indicates a timeout. The hostname was unreachable within the timeout period of 60 seconds.
- Ensure that monitored hostnames resolve correctly and are accessible to avoid false alerts.

## Negative Status Codes

Hostname monitoring shows a number of custom HTTP response codes beyond the standard. These response codes are based on [Chromium's response codes](https://source.chromium.org/chromium/chromium/src/+/main:net/base/net_error_list.h) and give you more details about error responses.

<!-- vale off -->

| Code | Error Code | Description |
|-------|--------------------------------------------------|---------------------------------------------------------------------------------------------------|
| -2 | net::ERR_FAILED | Generic network error |
| -3 | net::ERR_ABORTED | An operation was aborted (due to user action). |
| -7 | net::ERR_TIMED_OUT | Timed out |
| -10 | net::ERR_ACCESS_DENIED | Access denied |
| -20 | net::ERR_BLOCKED_BY_CLIENT | Blocked |
| -100 | net::ERR_CONNECTION_CLOSED | Connection was closed (TCP FIN) |
| -101 | net::ERR_CONNECTION_RESET | Connection was reset (TCP RST) |
| -102 | net::ERR_CONNECTION_REFUSED | Connection was refused |
| -103 | net::ERR_CONNECTION_ABORTED | Connection was aborted (no ACK received) |
| -104 | net::ERR_CONNECTION_FAILED | Connection attempt failed |
| -105 | net::ERR_NAME_NOT_RESOLVED | Host name could not be resolved |
| -106 | net::ERR_INTERNET_DISCONNECTED | Internet connection lost |
| -107 | net::ERR_SSL_PROTOCOL_ERROR | SSL protocol error |
| -108 | net::ERR_ADDRESS_INVALID | Invalid IP address and/or port number |
| -109 | net::ERR_ADDRESS_UNREACHABLE | Unreachable IP address |
| -110 | net::ERR_SSL_CLIENT_AUTH_CERT_NEEDED | Server requested a client certificate for SSL client authentication |
| -112 | net::ERR_NO_SSL_VERSIONS_ENABLED | No SSL protocol versions are enabled |
| -113 | net::ERR_SSL_VERSION_OR_CIPHER_MISMATCH | Client and server don't support a common SSL protocol version or cipher suite |
| -114 | net::ERR_SSL_RENEGOTIATION_REQUESTED | Server requested a renegotiation (re-handshake) |
| -116 | net::ERR_CERT_ERROR_IN_SSL_RENEGOTIATION | During SSL renegotiation (re-handshake), the server sent a certificate with an error |
| -117 | net::ERR_BAD_SSL_CLIENT_AUTH_CERT | SSL handshake failed because of a bad or missing client certificate |
| -118 | net::ERR_CONNECTION_TIMED_OUT | Timed out |
| -123 | net::ERR_SSL_NO_RENEGOTIATION | Peer sent an SSL no_renegotiation alert message |
| -138 | net::ERR_ACCESS_DENIED | Access denied |
| -141 | net::ERR_SSL_CLIENT_AUTH_SIGNATURE_FAILED | Unable to sign the CertificateVerify data of an SSL client auth handshake with the client certificate's private key |
| -145 | net::ERR_WS_PROTOCOL_ERROR | WebSocket protocol error - connection terminated due to a malformed frame or other protocol violation |
| -147 | net::ERR_ADDRESS_IN_USE | Failed to bind to an address because already in use |
| -148 | net::ERR_SSL_HANDSHAKE_NOT_COMPLETED | SSL handshake has not completed |
| -149 | net::ERR_SSL_BAD_PEER_PUBLIC_KEY | SSL peer's public key is invalid |
| -150 | net::ERR_SSL_PINNED_KEY_NOT_IN_CERT_CHAIN | Certificate didn't match built-in public key pins for the host name |
| -151 | net::ERR_CLIENT_AUTH_CERT_TYPE_UNSUPPORTED | Server request for client certificate did not contain any types we support |
| -152 | net::ERR_ORIGIN_BOUND_CERT_GENERATION_TYPE_MISMATCH | Server requested one type of cert, then requested a different type while the first was still being generated |
| -153 | net::ERR_SSL_DECRYPT_ERROR_ALERT | SSL peer sent us a fatal decrypt_error alert |
| -156 | net::ERR_SSL_SERVER_CERT_CHANGED | SSL server certificate changed in a renegotiation |
| -157 | net::ERR_SSL_INAPPROPRIATE_FALLBACK | SSL server indicated that an unnecessary TLS version fallback was performed |
| -158 | net::ERR_CT_NO_SCTS_VERIFIED_OK | All Signed Certificate Timestamps failed to verify |
| -159 | net::ERR_SSL_UNRECOGNIZED_NAME_ALERT | SSL server sent us a fatal unrecognized_name alert |
| -164 | net::ERR_SSL_CLIENT_AUTH_CERT_BAD_FORMAT | Failed to import a client certificate from the platform store into the SSL library |
| -165 | net::ERR_SSL_FALLBACK_BEYOND_MINIMUM_VERSION | SSL server requires falling back to a version older than the configured minimum fallback version |
| -166 | net::ERR_ICANN_NAME_COLLISION | Resolving a hostname to an IP address list included the IPv4 address "127.0.53.53". This is a special IP address which ICANN has recommended to indicate there was a name collision, and alert admins to a potential problem |
| -200 | net::ERR_CERT_COMMON_NAME_INVALID | Server responded with a certificate whose common name did not match the hostname |
| -201 | net::ERR_CERT_DATE_INVALID | Server responded with a certificate that is either expired or not valid yet |
| -202 | net::ERR_CERT_AUTHORITY_INVALID | Server responded with a certificate signed by an untrusted authority |
| -203 | net::ERR_CERT_CONTAINS_ERRORS | Server responded with a certificate that contains errors |
| -204 | net::ERR_CERT_NO_REVOCATION_MECHANISM | Certificate has no mechanism for determining if it is revoked |
| -205 | net::ERR_CERT_UNABLE_TO_CHECK_REVOCATION | Revocation information for the security certificate for this site is not available |
| -206 | net::ERR_CERT_REVOKED | Server responded with a certificate that has been revoked |
| -207 | net::ERR_CERT_INVALID | Server responded with a certificate that is invalid |
| -208 | net::ERR_CERT_WEAK_SIGNATURE_ALGORITHM | Server responded with a certificate that is signed using a weak signature algorithm |
| -210 | net::ERR_CERT_NON_UNIQUE_NAME | Host name specified in the certificate is not unique |
| -211 | net::ERR_CERT_WEAK_KEY | Server responded with a certificate that contains a weak key |
| -212 | net::ERR_CERT_NAME_CONSTRAINT_VIOLATION | Certificate claimed DNS names that are in violation of name constraints |
| -213 | net::ERR_CERT_VALIDITY_TOO_LONG | Certificate's validity period is too long |
| -324 | net::ERR_EMPTY_RESPONSE | Server closed the connection without sending any data |
| -803 | net::ERR_DNS_TIMED_OUT | DNS lookup timed out |
| -9999 | unknown error | Error not mapped |

<!-- vale on -->