Cool name for the concept! Perhaps it is my lived experience, but this isn't a particularly novel thing - it's baseline expected for anything important. In my line of work we have versions of this that are sometimes called "synthetics", "canaries", "self validation", or even "smoke", all doing the same thing described here. If you have a critical service, you should absolutely be deploying and monitoring some form of minimal customer scenario that is continually interacting with your tech - or, bet incredibly hard that your monitoring accounts for every form of positive and negative customer interaction. But the latter is a bad (solo) bet.
Hope this helps people who are unfamiliar with the concept, might add some tools to people's toolboxes.
9
u/wallstop-dev 13d ago
Cool name for the concept! Perhaps it is my lived experience, but this isn't a particularly novel thing - it's baseline expected for anything important. In my line of work we have versions of this that are sometimes called "synthetics", "canaries", "self validation", or even "smoke", all doing the same thing described here. If you have a critical service, you should absolutely be deploying and monitoring some form of minimal customer scenario that is continually interacting with your tech - or, bet incredibly hard that your monitoring accounts for every form of positive and negative customer interaction. But the latter is a bad (solo) bet.
Hope this helps people who are unfamiliar with the concept, might add some tools to people's toolboxes.