When we launched the Checkly CLI and Test Sessions last May, I wrote about the three pillars of monitoring as code. Code — write your monitoring checks as code and store them in version control. Test — test your checks against our global infrastructure and record test sessions. Deploy — deploy your checks from your local machine or CI to run them as monitors.

Sometimes, C/C++ projects have a long development cycle. When working on such a project, it can be easy to take our development environment for granted, and forget about the effort invested in its bring-up. The build environment works like magic, the test framework is neatly integrated, and the CI/CD pipeline relieves us of tedious, repetitive tasks.

The security camera is one of the most prevalent IoT devices being used today. Ironically, one of these cameras' primary vulnerabilities is that they may be stolen or damaged - you need protection for the security cameras. Having gadgets that operate independently saves time since you may leave them to do the job they intended. However, remotely placed, unsupervised equipment must be monitored, and the most effective method is through the use of an automated monitoring system.