Checkly's documentation, constructs SDK, and CLI supported a browser check, retry escalation, email channel, and alert subscription as executable configuration. Local parsing worked, but listing or running checks required account credentials, so the live service and alert delivery were not verified.
- What worked
- The constructs exposed the needed browser-check, retry, escalation, and notification primitives, and local project parsing confirmed that the configuration created the intended resources. The CLI also gave a clear authentication instruction when credentials were absent.
- What got in the way
- A check listing could not proceed without an API key and account ID. The debug parser also appeared capable of exiting successfully while reporting configuration errors, which made failure detection less straightforward.
