2020 was an unpredictable year that presented several challenges, such as the outbreak of the coronavirus (COVID-19) pandemic. As part of the “new normal,” the world has adopted infection prevention procedures. The 2020 calendar year was defined by face coverings, constant sanitization and physical distancing. At its core, the year was an exhausting, surreal 12-month period for many.

As the pandemic wears on, remote incident management has become the norm worldwide for businesses. Here we share some best practices that helped us to address remote incidents and make on-call less stressful. With the onset of remote work due to Covid-19, remote incident management has become the norm for businesses worldwide. Organisations that were earlier used to having war rooms now find themselves having to coordinate teams through Slack, MS Teams or other collaboration tools.

If you’re a veteran in this space, you probably understand the many incident response metrics and concepts, along with the many (at times exasperating) acronyms. For those new to the space, or even those with years of experience, the terminology is often overwhelming. If you’re one of those people who’s struggling to navigate through the world of DevOps metrics, we’ve created this article for you.

We are thrilled to begin the year on a high note! Squadcast has been awarded in the Incident management and IT Alerting category in G2's Winter Report 2021 for below categories. ‍‍ “We are honoured to be recognised as a Momentum Leader in the IT Incident management category by G2. We have always strived to create the fastest and easiest Incident Response experience for Engineering and DevOps teams that enables organisations to better monitor their IT infrastructure and applications.

Managed service providers (MSPs) require automation, so they can deliver fast, efficient IT services that meet customer expectations. But, MSP automation can be difficult — and the longer it takes an MSP to automate IT service management (ITSM), the further it falls behind its competitors. Today’s MSPs face several challenges relative to automation, including: 1. Complex Scripting Language IT technicians may need to learn a complex scripting language to leverage an ITSM platform.

One of the most versatile and foundational SRE tools is the SLO, or service level objective. The SLO is a threshold set for key reliability metrics. When incidents push the metric over the threshold, a response launches to prevent further damage. Conversely, as long as you meet your SLO, you can continue to ship new code. The space you have before you breach this threshold is the error budget.

As reliability shifts left, more companies are adopting SRE best practices. These best practices don’t only include conducting incident retrospectives. The heart and soul of these best practices are a blameless culture and a desire to grow from each incident. In a recent industry leaders’ roundtable hosted by Blameless, top experts discussed how teams can embrace SRE best practices and make cultural shifts towards blamelessness.

You have a web site, app, online shop, or SaaS offering? Then you have plenty of user actions. That can be visiting a certain page, signing up for a service or canceling a subscription. Wouldn’t it be great to know in real time when an important customer action takes place? This would allow you sales, customer service or technical teams to act immediately no matter where they are.

Every second counts when it comes to Managed Service Provider (MSP) security — the longer it takes an MSP to complete security incident response, the greater the ramifications of the incident on the service provider and its stakeholders. When faced with a cyber attack, it’s crucial to understand the potential consequences of the security incident. It also is paramount for an MSP to establish a plan, so it can quickly and effectively respond to cyber attacks and other security incidents.