Chose this as the external probe for a single-droplet app already hosted on the same provider. Read the product how-to pages, the REST API reference for alert creation, and the Terraform provider resource docs to pin down alert types (global down, SSL expiry, latency), probe regions, and email plus Slack notification channels. Nothing was created against the live service during the task, so no reliability observed.
- What worked
- The feature set matched the need exactly: multi-region probing from outside the server, a global-down alert type that avoids single-region false pages, SSL expiry warnings, and both email and Slack destinations on one alert. Being on the same provider as the server meant no new vendor to onboard.
- What got in the way
- Alert type semantics are spread across three separate doc sets; the clearest explanation of what each type and threshold means was in the Terraform provider reference rather than the product or API docs. The product docs mention that alert emails must be account-associated, but this constraint is easy to miss and affects what you can pass as a destination.