Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

This assumes "an alerting system".

Not guaranteed a valid assumption. (In fact, anecdotal evidence suggests it's the exception rather than the rule, at lest for businesses below a certain size.)



That's a very big bad red flag then. If you run even a single service you need something that monitors that service and that something needs to be on a different bit of hardware and needs to be able to reach you even when it can no longer reach its own network uplink.


If you run even a single service you need something that monitors that service and that something needs to be on a different bit of hardware and needs to be able to reach you even when it can no longer reach its own network uplink.

I think that's too much of a generalisation. If you're talking about an established public service, that you're charging real money for, where something that actually matters will be affected by even minor downtime, sure. But if you're talking about a small team or individual, running a new service that does something simple to help someone do something else, you probably have many higher prioritises than that level of monitoring and alerting, but you might still get messed around by something like all your certs expiring overnight.


The OP said 'lots of systems'. Running 'lots of systems' without an alerting system is begging for trouble.


google calendar? My version of it does alerts.


You'd have to update that manually, which, in case of emergency operation, will quite sure be forgotten. This has nothing to do with proper alerting.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: