Operations | Monitoring | ITSM | DevOps | Cloud

A new year is a chance to have a new start, and one thing that it’s a great opportunity to think about is the monitoring and observability platform you’re using for your applications. If you’ve been using a legacy monitoring system, you’ve probably heard about observability all over the ‘net and want to figure out if this is really something you need to care about.

A cynical network engineer might say, “configuration drift happens when you take the day off.” Someone changed something they shouldn’t have, and didn’t tell anyone. As a result, the network gets just a little less secure, and a little harder to troubleshoot. And then it happens again. And again. And over time, all those little changes that people thought would never mean anything suddenly add up to a network looking a lot different from what it’s supposed to be.

When I’m speaking to any IT solution provider or managed service provider (MSP), one of the most common questions I’m asked is, “What’s the one mistake you’d recommend any IT businesses avoid?” My answer is always this: Not documenting your business. The reason is simple. If you don’t document your business, you’ll inevitably find your business is prone to an SPF—a single point of failure.

As a DevOps, SecOps, or IT operations manager, you're surrounded by all the technology for the systems running the entire organization. This means legacy infrastructure, multi-cloud environments, services, tools, and applications. All of these components generate data—a huge amount of data—some of which you need to leverage for full-stack observability to ensure those systems supporting the business are running efficiently.

Founded in 1884 and located in Ghent, Belgium, Algist Bruggeman supplies fresh, liquid, and dried yeast to industrial, semi-artisanal, and artisanal bakeries, as well as to the beer, wine, and pharma industries. Algist Bruggeman is part of the Lesaffre Group, a key global player in fermentation for more than a century. Even with more than a century of industrial production behind it, Algist Bruggeman continues to evolve its manufacturing processes.

Serverless has become an increasingly popular paradigm among organizations looking to modernize their applications as it allows them to increase agility while reducing their operational overhead and costs. But the highly distributed nature of serverless architectures requires developers to rethink their approach to application design and development. AWS-based serverless applications hinge on AWS Lambda functions, which are stateless and ephemeral by design.

In part 1 of this series, we looked at common design principles and patterns for assembling microservices in serverless environments. But when it comes to building serverless applications, designing your architecture is only part of the challenge. You also have to ensure that each of your individual functions and services are secure, reliable, and highly performant—without incurring enormous costs.

In between online meetings and chat conversations, we've all embraced the digital way of life and work, and it is here to stay. We may not know any other way to operate businesses in a few years' time except the digital space. This way of life will require clear communication channels for businesses to connect with their users. Keeping that in mind, as well as your feedback in our community, we've shaped StatusIQ to help ease the incident communication process.

Today OpsLogix announces the upcoming release of their new Kubernetes Management Pack. This product is designed to help organizations monitor their Kubernetes clusters using System Center Operations Manager (SCOM). The management pack provides comprehensive monitoring of all aspects of your Kubernetes environment, from individual nodes and pods to entire clusters.