Operations | Monitoring | ITSM | DevOps | Cloud

Time flies and Healthchecks.io is already 6 years old. Here’s a quick review of notable recent events and the project’s current state.

More and more cloud providers are emerging and spreading their business across different regions in the current times. As a result, customers want to reduce their IT workload and migrate their product or application to a cloud-based environment. The primary reason behind this is that the cloud heavily reduces the overheads of investing in IT infrastructure, hardware upgrades, maintenance, etc.

DevOps and SRE are domains with rapid growth and frequent innovations. With this blog you can explore the latest trends in DevOps, SRE and stay ahead of the curve. The past decade has seen widespread adoption of DevOps methodologies in software development. Unsurprisingly, as the needs of users change, DevOps techniques have evolved as well. In this blog we will look at the trends that are most likely to have a significant impact in the coming years.

Current observability practice is largely based on manual instrumentation, which requires adding code in relevant points in the user’s business logic code to generate telemetry data. This can become quite burdensome and create a barrier to entry for many wishing to implement observability in their environment. This is especially true in Kubernetes environments and microservices architecture.

Communications Service Providers around the world have experienced an unprecedented explosion in demand for bandwidth due to several driving forces including more video streaming, the growing popularity in areas like cloud gaming and the increasing move to the cloud to name a few.

Being alerted to an issue with your application before your customers experience undue interruption is a goal of every development and operations team. While methods for identifying problems exist in many forms, including uptime checks and application tracing, alerts on logs is a prominent method for issue detection. Previously, Cloud Logging only supported alerts on error logs and log-based metrics, but that was not robust enough for most application teams.

While unit testing and integration testing can give you insight into the individual functionalities of an application, “at times you need some sort of monitoring or testing mechanism which also simulates a user’s behavior to test how the application would work or look to an actual user in the world,” says Grofers Software Development Engineer Yashvardhan Kukreja. That’s where synthetic monitoring comes in.

If a customer has an issue with any part of Microsoft 365, MSPs just don’t have the native visibility to identify the root cause, let alone respond to and remediate the problem. Most of the time, it’s little more than checking Microsoft’s Service Health status to see if Microsoft knows it’s having a problem.

4 best practices for breaking down silos and establishing a culture of shared responsibility toward reliability.

We’ve seen a number of MSPs hesitant to dive into using Microsoft Intune for their customers. One reason for this is that it may require them to encourage customers toward Microsoft 365 Business Premium, which, at an additional cost per seat, may seem like a tall order for a client for a 30-person team. It’s also a new discipline for many technicians, and often requires they find time to hone their skills while tackling existing tickets throughout a normal day.