Operations | Monitoring | ITSM | DevOps | Cloud

On December 31, 2008, all the Microsoft Zunes around the world stopped working. The development team hadn’t properly accounted for the Leap Year, and when the year changed over, everything broke. On February 29, 2024, card payments in a Swedish grocery chain went down, payment terminals in New Zealand gas stations crashed, and an EA Sports racing game was rendered unplayable for the day.

With the digital world changing faster than ever, businesses are rushing to keep up, especially when it comes to supporting remote work. Interestingly, a report from 2023 highlighted that over 82% of businesses now support some form of remote work, underscoring the critical role of effective RMM solutions today. This makes choosing the right remote monitoring and management (RMM) tools more important than ever.

Since containers revolutionized resources utilization and their cost by significantly increasing VM densities, understanding Azure Container Instance Pricing is key for making informed decisions about your containerized apps. ACI is the serverless option within Azure, to provision additional compute for demanding and highly scalable workloads. Knowing the ACI pricing, you can optimize costs while efficiently deploying your containers in a managed service that will optimize your operations.

In an earlier blog, we looked at slow dependencies and how they can impact the reliability of other services. While we explored what happens when dependencies are degraded, what happens when dependencies outright fail? What can you do when your application or service sends a request to another service, and nothing comes back? We’ll answer this question by using Gremlin to proactively test a service with multiple dependencies.

Figuring out how to represent your as-built environment in PagerDuty can be confusing for new users. There are a lot of components to PagerDuty that will help your team be successful managing incidents, integrating with other systems in your environment, running workflows, and using automation. Your organization might have a lot of these components – users, teams, services, integrations, orchestrations, etc.

There’s no two ways about it: on-call is stressful. But with humans at the center, it’s especially important to find ways to make it as manageable and empathetic as possible. In this webinar with our friends at ELC, incident.io VP of Engineering, Noberto Lopes, and Intercom Staff Product Engineer, Andrej Blagojević, discuss their own experiences with on-call, and how the process can be better.