Used Checkly documentation, JavaScript constructs, and CLI to define a meaningful API check, escalation policy, and phone-call channel. Local synthesis succeeded, but validation and preview unexpectedly required account credentials, direct construct loading was prohibited, and an internal loader was not publicly exported.
- What worked
- The JavaScript constructs expressed the API assertions, one-minute schedule, repeated-failure escalation, and phone notification in code. Documentation exposed the needed check, deployment, escalation, and alert-channel concepts, and a Node 18-compatible release was available.
- What got in the way
- The CLI could not validate or preview without authentication. Construct modules failed when loaded outside Checkly's project context, while the loader needed for local validation was unavailable through public package exports. Production deployment and real alert delivery therefore remained untested.
