Leverage Multiple Alert Sources in Squadcast to reflect your actual system infrastructure on your Service Dashboard Having your Incident Management Tool reflect your system architecture is a big milestone in reducing cognitive load on your on-call team. In order to help our users move one step closer to this milestone, we recently released the functionality to add multiple alert sources to a service. You can now model your service dashboard to mimic your actual system architecture.

An incident postmortem is not only an essential document for reference, but also necessary as a process by which teams can collaboratively learn from failure, and communicate independent learnings across the organization.

You deployed a service to your Kubernetes cluster. How do you it is working as expected? In this blog, Gigi Sayfan, author of “Mastering Kubernetes” talks about Kubernetes observability tools like Prometheus, Grafana and Jaeger, how to utilize them to set proper SLOs and make sure the service meets its objectives.

Reducing alert fatigue starts from your monitoring platform - setting the right thresholds to trigger alerts and understanding which of these are essential to be sent into your on-call platform is a start. This post outlines some of the best practices that help you reduce alert noise and improve your on-call experience. The word noise implies something unpleasant and unwanted. You combine that with on-call and it adds a factor of annoyance to the already overwhelming process.

At Squadcast, we use Grafana and absolutely love it! This blog post talks about how you can use your Grafana data to set off alert triggers in Squadcast. Turbocharge your observability data in Grafana by making it actionable.

Atlassian’s Jira is an issue and project tracking software that helps plan, track and manage projects. Jira is also used by customers and internal teams to log issue tickets for the product and engineering teams to look into and resolve. This forms a feedback loop between the customer-facing and product teams to help drive and deliver the best possible software. Jira is widely adopted by Agile development teams to customize workflows and embrace collaborative resolutions to ship good software fast.

The unexpected and sudden shift to remote working introduces a new set of problems within the incident response space. And while each organization needs to take its own unique circumstances into account, this post outlines the best practices and steps that can be taken in the right direction in keeping operations both productive and proactive.

Here's a curated list of “Must Read” books specific to the Incident Management space, suggested by folks from the SRE and DevOps community to help you understand what changed their perspective of software engineering as a role.

Monitoring has moved from a simple proactive practice to a necessity on any product launch checklist. It is crucial to pick a tool that meets your observability needs & ensures reliability of your service to your customers. Over the years, with an increase in adoption of DevOps and SRE practices, Monitoring has moved from a simple proactive practice to a necessity on any product launch checklist.

In this blog, Danny Mican, a Senior Site Reliability Engineer, outlines how to implement SLOs from scratch using the IIDARR process. He also states it is extremely crucial for your SLOs to be actionable and is always following a feedback approach as it will play an important role in the debate of Features Vs Technical Debt.