Category / Incident Response / Kubernetes / Service Health
-
![Stethascope and mask]()
Building a Healthcheck RunBook: Analysis of K8s Logs
There’s nothing worse than an outage. Every outage has a cost – both in revenue, sales, but also reputation and perceived reliability. No one wants their company to appear in the news…
-
![]()
DNS: Is your domain healthy?
DNS: Is your domain healthy? When your website goes down, you risk losing customers, revenue, and credibility. When there is an issue — it is critical to know as quickly as possible… -
![]()
Part 3 – Proactive Diagnostics and Remediation for Platform Reliability and Incident Response
In our first post we answered how you can start or improve your incident response using runbook automation in your organization. The second post gives you a framework for evaluating processes…
-
![]()
SecOps Automation: Reminder for SSL Certificate Renewal
These days, there is no excuse not to enable HTTPS for your website. In fact, it is mandated by Google in early 2018. As per the report given by major certificate issuing authorities,… -
![]()
Part 2 — Best Practices for Modern Incident Response: Why Monitoring, Alerting and Remediation are Not Enough
This second post in a 3-part series specifically looks into the ways leading organizations handle incident response today. In our first post we answered how you can start or improve your incident response using… -
![]()
Have you ever: Built a Service Health Check
Most of the tech giants including companies like Amazon, Netflix, started to build their systems using a monolithic architecturebecause back in the time it was much faster to set up a monolith…
Loading posts...
