|
|
|
|
|
by beebs93
2416 days ago
|
|
Every company I've been with seems to re-invent the terms or swich their definitions slightly. For me, currently, "canary" means a set of basic automated integration tests that are continually running in production with alarms that feed into a master aggregate "switch". Wether the dedicated canary accounts end up hitting a one-box prod host or real prod host in the end isn't a factor. The important thing is we incrementally expose our latest code commit to prod hosts via one-boxing to reduce the customer exposure if an acute problem somehow gets past the previous code deploy stages/tests. |
|
this sounds roughly like synthetic monitoring:
https://en.wikipedia.org/wiki/Synthetic_monitoring
synthetic in the sense of synthetic traffic, since it isn't traffic from genuine users.
Can you go into more detail about what is meant by this:
> alarms that feed into a master aggregate "switch"
what is the master aggregate "switch" ? what does it do?