Adding alerts across your monitoring tools is taking a proactive approach to reliability. But if there are too many alerts, then it can become counterproductive because team members will start ignoring alerts or remove the alerting altogether. Which is why you need a systematic approach to adding alerts and dealing with them.
Kubernetes is hard, but lets make monitoring and alerting for Kubernetes simple! At iLert we are creating architectures composed of microservices and serverless functions that scale massively and seamlessly to guarantee our customers uninterrupted access to our services. As many others in the industry we are relying on Kubernetes when it comes to the orchestration of our services.
If you've ever had to be on the receiving end of a monitoring system that uses email for alerts, you know how noisy things can get. Particularly if you're working in an agency or freelance-like environment, with dozens of client sites to maintain. You get so many emails that you start looking into integrations with third-party services like Zapier, and coming up with more and more complex rules to try reduce the noise.
When DevOps teams talk about monitoring a database, the primary motivation is to ensure that the database won’t suffer a performance hiccup. Long queries, timeouts and table scans are among the most popular causes behind lousy customer experience. However, in recent years, more data has been shifted to cloud databases.
Learn how to monitor an API by doing an HTTP POST request to it every minute and instantly be notified when it goes down. It all takes under 10 minutes so let’s dive in, head first.