The classic answer is a monitoring platform: ....... All great tools. But for a few dozen checks, I did not want to operate a second distributed system just to know whether the first one is up.
There is advantage to keeping to "classic" tooling especially if you are not in an "I" context but in a "team" context. How large is the team that is going to use and maintain this custom tooling?
Comments
There is advantage to keeping to "classic" tooling especially if you are not in an "I" context but in a "team" context. How large is the team that is going to use and maintain this custom tooling?
It s a tradeoff, here we have 20 products, 2 devs. There is less maintenance in such small tool, than in classic prometus/graphana/zabbix.
This is exactly what I say, use "classic" tooling in a team. No need of a panzerfaust to kill a mosquito.