Software Alerting maturity levels
Over the years i have been part of several incident responses in production and pre-production environments for Software as a Service (SaaS) products. I have observed significant variations amongst teams w.r.t. their Alerting setup and processes. After some thought i came up with below Alerting maturity level starting from lowest to highest. 1. Team doesn't have any monitoring dashboards to monitor it's services in production or pre-production environments. Essentially, monitoring is considered low-priority as the team is "too busy" building new features. I have seen this trade-off in startups still trying to find product market fit. Another reason for this situation is "luckily" the team hasn't had production incidents - maybe due to low usage or less complex software. Once a company starts to have real users then it's time to invest in setting up monitoring dashboards. 2. Team has monitoring dashboards for Production env only but not pre-pro