What is the error alerting stack at your startup?
If you are working at a < 30 people engineering team company what is the alerting stack that you guys are using ?
We tend to miss a lit of critical alerts that come to simply because the alerting is not set up properly.
Nothing fancy, Alerts are posted in a slack channel.
Uptime monitoring + cron job monitoring via OnlineOrNot (dogfooding my own product), with alerts going to PagerDuty (set up to email -> SMS -> call me if I don't acknowledge), and a "public" alert in a Slack channel.
StatusCake has a feature to call me. It's a horrible artificial voice "your website $name is down" but I'm fine with anybody shouting at me at 3am. The phone number is from the United States and I don't need to add it to my phone book because that's the only US phone calling me. (For people inside the US you might think it's another robocall)
We have someone check grafana a few times a day and alert us if there's an issue. Not great, but it works
Custom built monitoring on top of CloudWatch logs: we subscribe to the log groups and parse the logs.
Errors are reported in dedicated slack channels
The “MVP” was built in 1 week after we were faced with an outrageous bill from an observability vendor and decided to give a shot at implementing it ourselves.
It has worked extremely well for us and has needed little maintenance (granted we pay AWS to not have to do that maintenance)