Operations | Monitoring | ITSM | DevOps | Cloud

December 2022

Sponsored Post

SLA Vs SLO: Tutorial & Examples

Service level agreements (SLA) and service level objectives (SLO) are increasing in popularity because modern applications rely on a complex web of sub-services such as public cloud services and third-party APIs to operate, making service quality measurement an operational necessity for serving a demanding market. This article focuses on the similarities and differences between SLAs and SLOs, explains the intricacies involved in implementing them, presents a case study, and finally recommends industry best practices for implementing them.

Looking back at our journey through 2022

We are on the cusp of breaking into 2023🗓️with a bag full of interesting memories. Before we wrap up this year end's celebrations we'd like to look back and highlight some notable events that took place at Squadcast. ‍ Squadcast has grown leaps and bounds over the 12 months in our journey towards becoming an integrated Reliability Workflow platform. 😎

15 DevOps and SRE Tools you Should Know About in 2023

With the constantly evolving landscape of technology, professionals in the DevOps and SRE fields need to stay up-to-date and knowledgeable about the tools and practices driving the industry forward. Whether you are just starting your career or have been working in DevOps or SRE for years, this post will provide valuable insights and information on the tools you should be familiar with as we head into 2023.

Squadcast + Hund Integration: A Simplified Approach for effective Alert Routing

Hund is a versatile Service Monitoring & Communication tool. It helps monitor services and keeps your audience informed about any status changes automatically through a status page. If you use Hund for monitoring and management requirements, you can integrate it with Squadcast, an end-to-end incident response tool, to route detailed alerts from Hund to the right users in Squadcast.

Getting Amazon GuardDuty alerts via SNS Endpoint

Monitoring your infrastructure and safeguarding it against threats is not easy. Setting up the infrastructure, monitoring, collecting and analyzing information for threat detection, is indeed a cumbersome process. This is where a security monitoring service like Amazon GuardDuty can help. In this blog, we will explore Amazon GaurdDuty service and discuss how integrating it with Squadcast can help you route alerts to the right users for quick and efficient incident response.

Maximize efficiency with Terraformer: Manage Squadcast resources via IaC

Ever since Terraform was first launched by HashiCorp, infrastructure teams have been quick to leverage its functionality. Because deploying infrastructure via code became so much easier and error-free. This surely became a great way to deploy new infrastructure with custom configurations, but what about managing cloud infrastructure that is already defined? Can Terraform be used to make changes to them? Or can it be used to deploy the same configurations to new environments?

Assessing Observability Maturity at Danske Bank

In order to ensure reliability, IT operations teams today require a deeper understanding of systems than monitoring, along, can provide. In this session, you'll hear insights from Danske Bank about how their observability journey started, the obstacles encountered along the way, what they've achieved in observability so far and, finally, how they measure the maturity of their observability practice.
Sponsored Post

SRE Best Practices

Site Reliability Engineering (SRE) is a practice that emerged at Google because of its need for highly reliable and scalable systems. SRE unifies operations and development teams and implements DevOps principles to ensure system reliability, scalability, and performance. There's plenty of documentation on tactics for adopting automation and implementing infrastructure as code, but practical ops-focused SRE best practices based on real-world experience are harder to find. This article will explore 6 SRE best practices based on feedback from SREs and technical subject matter experts.

Introduction to Kubernetes Imperative Commands

Kubernetes was born out of the need to make our complex applications highly available, scalable, portable and deployable in small microservices independently. It also extends its capabilities to make adoption of DevOps processes and helps you set up modern Incident Response strategies to enhance the reliability of your applications.

Creating Routing Rules I Creating Incident Routing Flows I Alert Routing I Event Tags I Squadcast

Alert Routing allows you to configure Routing Rules to ensure that alerts are routed to the right responder with the help of event tags attached to them. This video explains how you can utilise Routing rules to create various incident routing flows.

Integrating Slack & Squadcast- Trigger, Acknowledge, Resolve & Reassign incidents from Slack channel

You can integrate Squadcast and Slack to collaborate efficiently with your team while working on incidents. Squadcast sends a notification to the configured Slack Channel as soon as an incident is triggered.

Alert Suppression Rules in Squadcast to prevent Alert fatigue | Squadcast

Alert suppression can help you avoid alert fatigue by suppressing notifications for non-actionable alerts. Squadcast will suppress the incidents that match any of the Suppression Rules you create for your Services. These incidents will go into the Suppressed state and you will not get any notifications for them.

Using StatusPage at squadcast | SRE Best practices | Squadcast

Let your customers know how your Services are doing, without them having to ask you about it. One of the core principles of SRE is Transparency and Status Pages help you communicate the status of your Services to your customers at all times, as opposed to you getting to know the status of your Services through support tickets logged by your customers.

Plesk 360 + Squadcast: Alert Routing Made Easy

Plesk is a popular web hosting platform that makes it easier for administrators to set up and manage websites. Its offering Plesk 360 empowers users to Monitor & Manage Servers more effectively. With its features like fully integrated site & server monitoring helps users keep track of performance and prevent downtime.

Tagging & Routing at Squadcast | Incident Management | Squadcast

Event Tagging is a rule-based, auto-tagging system with which you can define customized tags based on incident payloads, that get automatically assigned to incidents when they are triggered. Auto-add relevant information like priority, severity or alert type to make incoming incidents context-rich. Route alerts to the right responder(s) based on the tags they carry

Escalation Policy I Round Robin & Advanced Escalations I Incident Assignment Strategies I Squadcast

An escalation policy is a collection of rules used to define how and when an incident should be escalated. In Squadcast an Incident escalation happens when a responder hands off the task/incident to another member, and this handoff is subject to specific rules. This video explains how to set up Escalation Policies, and Round Robin Incident Assignment Strategy in Squadcast.

Integrating Microsoft Teams & Squadcast - Acknowledge, Resolve & Reassign Incidents | Squadcast

Teams using MS Teams can now integrate with Squadcast and easily Acknowledge, Resolve & Reassign incidents using MS Teams. You can configure Squadcast to send a notification to the configured MS Teams channel as soon as an incident is triggered.

APImetrics + Squadcast: Routing Alerts Made Easy

APImetrics is an API Compliance, Monitoring and Security solution that lets you make and run API calls or sequences of API calls (workflows) from external, remote cloud locations using exactly the same security configurations as a typical end user would use. If you use APImetrics for API calling requirements, you can integrate it with Squadcast, an end-to-end incident response tool, to route detailed alerts from APImetrics to the right users in Squadcast.

SRE Maturity Model: How Do You Assess Your Team?

How do you evaluate your SRE team’s progress in implementing SRE? We discuss the key SRE indicators for evaluating your team’s progress in the SRE maturity model. ‍ What is the SRE maturity model? ‍ The SRE maturity model is a way of judging how far you are in implementing SRE principles. It is a method used by teams to understand where they ought to implement more SRE best practices to reach greater SRE maturity.

Observability Pipelines for an SRE

In data management, numerous roles rely on and regularly use observability data. The Site Reliability Engineer is one of these roles. Site Reliability Engineers (SREs) work on the digital frontlines, ensuring performant experiences by using observability data to maintain stability and awareness of software running in various environments across organizations.

How to design an effective incident on-call program

If anyone on your team has paged a colleague in the middle of the night, your DevOps team has an incident on-call program. Whether that team member knew who to page, and felt comfortable sending the page, is indicative of your on-call program's effectiveness. Join Thai Wood, founder of Resilience Roundup, and Matt Davis, SRE Advocate at Blameless, to discuss: This webinar was recorded live on December 13, 2022.

Using Squadcast's SLO Tracker | Error Budget | Setting up SLOs and configuring SLIs | Squadcast

With Squadcast, you can define and monitor Service Level Objects for your services. SLOs allow you to define and enforce an agreement between two parties regarding the delivery of a given service. A Service Level Objective (SLO) is a reliability target, measured by a Service Level Indicator (SLI), and sometimes serves as a safeguard for a Service Level Agreement (SLA). SLOs represent customer happiness and guide the development team’s velocity.

Introduction to Service Catalog | Service Ownership | Service Classification | Squadcast

To make service management a breeze, we bring to you our improved Service Catalog. The Service Catalog is designed to improve Service Classification and bring more transparency to Service Ownership within your org. This video explains how a consolidated summary of all active services from a single dashboard can help you better track your service health.

Tag You're It: Organized, Configurable Tagging is a Must-do for Great Incident Analytics.

Wouldn’t it be nice to learn which parts of your service see the most incidents, or why one service experiences more Sev1 incidents than the others? It’s not always easy to see the full disruptive impact of an engineering incident. Even harder to see trends across incidents and over time. Developing incident insights that you can use to help guide and shape the way your team designs and operates your product takes time, careful consideration, team engagement and the right tooling.
Sponsored Post

Outages ITOps professionals are thankful to avoid

As we settle into the time of year when we reflect on what we're thankful for, we tend to focus on important basics such as health, family and friends. But on a professional level, IT operations (ITOps) practitioners are thankful to avoid disastrous outages that can cause confusion, frustration, lost revenue and damaged reputations. The very last thing ITOps, network operations center (NOC) or site reliability engineering (SRE) teams want while eating their turkey and enjoying time with family is to get paged about an outage. These can be extremely costly - $12,913 per minute, in fact, and up to $1.5 million per hour for larger organizations.

Toil: Still Plaguing Engineering Teams

Our industry has always had localized expressions for work that was necessary but didn’t move the company forward. The SRE movement calls this type of work “toil.” The concept of toil is a unifying force because it provides an impartial framework for identifying — then containing — the work that takes up our time, blocks people from fulfilling their engineering potential, and doesn’t move the company forward.