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.