Operations | Monitoring | ITSM | DevOps | Cloud

Setting up OpenCost with Levitate to monitor the cost of Kubernetes clusters.

Navigating an extensive excel sheet to determine On-Call schedules and vacation plans can be daunting. The struggle of maintaining On-Call Schedules manually is real. But we've got a solution that can help. This blog addresses the challenges associated with manualOn Call Scheduling processes.

Understanding SRE metrics and how they impact your platform's availability are fundamentals of Site Reliability Engineering. How available is your website, service, or platform? What must you monitor and measure to ensure availability? How do you translate uptime into availability? This chart has numbers that every Site Reliability Engineer (SRE) should know.

If you’re an SRE, then you already know your SLOs from your SLAs, not to mention your SLIs. But even if you’re not au fait with those acronyms, you’ll soon discover how widespread and applicable these concepts are in this installment of our IPM Best Practices Series. We’ll explore these concepts in detail and explore how external monitoring can enhance the tracking of Service Level Objectives (SLOs), leading to positive user experiences and informed decision-making.

Critical information during Incident Management includes the incident's nature, impact, urgency, affected systems, and current status, enabling efficient resolution. Yet, the excessive details in incident notifications frequently hinders rather than aiding the process.

Whether you're a system administrator, a developer, or any other DevOps or Site Reliability Engineering (SRE) professional, you know that staying ahead in cloud-native computing is crucial. One way to keep your competitive edge in the technology game is to embrace the benefits of eBPF (Extended Berkeley Packet Filter). On top of advances in security and networking, eBPF-based tools are particularly impacting the observability landscape.

The IT world thrives on uptime, efficiency, and seamless experiences. But amidst software and servers, glitches and disruptions threaten to bring operations to a halt. When these disruptions arrive, Incident Management takes center stage, collecting resources to restore order and minimize the chaos. Yet, simply fixing the immediate issue isn't enough. Preventing future disruptions requires delving deeper, finding the root cause, the reason that triggered the incident.

In today's fast-paced digital landscape, ensuring the reliability of services is paramount for businesses aiming to deliver seamless user experiences. However, as the complexity of companies' environments grows, ensuring your services, infrastructure and applications are reliable and resilient to failure is challenging. It’s naive to think all services and infrastructure are operating 100% as designed.

Did you know, only 40% of companies with 100 employees or less have an Incident Response plan in place? Does that include you too? Even if it doesn't, this blog post is for you. Explore the Incident Management processes, best practices and steps so you can compare how your current IR process looks like and if you need to revamp it.