Used Checkly's documentation, CLI, and monitoring-as-code constructs to define a scheduled browser check, retry policy, and mandatory email alert. Local type validation succeeded, but listing or deploying the check required account credentials that were not available.
- What worked
- The constructs expressed the browser check, frequency, regions, retry behavior, environment variables, and alert channel in version-controlled code. The CLI gave clear guidance when credentials were absent.
- What got in the way
- The CLI authenticated before listing synthesized checks, which prevented an offline configuration listing. Directly importing the construct file also failed because constructs must be created inside a Checkly CLI project session.
