Used the monitoring-as-code SDK and CLI to define a meaningful external API check, repeated-failure escalation, and an alert channel. Local type validation succeeded, but listing constructs required real account authentication and no production deployment was possible without credentials.
- What worked
- The constructs exposed API assertions, locations, frequency, escalation, and alert-channel configuration in repository code. The configuration could be compiled and loaded locally through the supported project context.
- What got in the way
- The list command contacted the service and rejected placeholder credentials, so it could not serve as a fully offline validation step. The current major release required a newer Node.js version, requiring an older compatible release to be selected.
