Operations | Monitoring | ITSM | DevOps | Cloud

Overprovisioning or underprovisioning your Kubernetes resources can have significant consequences on both your budget and your app performance. By underprovisioning your Kubernetes infrastructure, you’ll end up with lagging, underperforming, unstable, or non-functional applications. On the opposite end of the spectrum, overprovisioning is a costly issue: Organizations spent almost $500 billion on cloud resources in 2022, yet an estimated 30% of those were wasted.

Many developers and product teams are iterating faster and deploying more frequently to meet user expectations for responsive and optimized apps. These constant deployments—which can number in the dozens or even hundreds per day for larger organizations—are essential for keeping your customer base engaged and delighted. However, they also make it harder to pinpoint the exact deployment that led to a rise in errors, a new error, or a performance regression in your app.

So you're used to debugging systems using a distributed trace, but your system is about to introduce a message queue—and that will work the same… right? Unfortunately, in a lot of implementations, this isn't the case. In this post, we'll talk about trace propagation (manual and OpenTelemetry), W3C tracing, and also where a trace might start and finish.

Data is kind of like Newton’s first law of motion. Data is just that unless acted upon by something else. Time series data, therefore, is something you derive from data. We generally derive time series data to record historical observations about a physical or virtual system (for example, think of sensors and servers, respectively). However, not all time series data is the same. There are different use cases for time series data, and each has its own workload needs.

Organizations are on a path to increased and improved digitization, with hundreds of applications, services, microservices and servers running in a multi-cloud or hybrid environment. As IT looks to move away from operations, they are turning to AIOps to ensure compliance, cybersecurity and threat management.

The third and final chapter in our three part blog series. John Appleby sits down with Nick Miletich, CTO at Managecore, to discuss how building a next generation managed service firm had to include automation at the helm.

Since the release of OpenSSL 3 and the adoption of the technology in recent Linux kernels, a growing demand for support in System Center Operations Manager and its cross-platform agents has emerged. Together with our clients, we have been waiting and hoping for a newer release to help them monitor these newer distributions in SCOM. And now it finally looks like the wait is over.

Are you concerned about the security of your website or online business? Do you want to ensure that your customers can trust your site and transact with you safely? If so, then you need to know about SSL certificate monitoring! SSL certificate monitoring is the process of continuously monitoring SSL certificates for potential vulnerabilities or incidents, such as certificate revocation or expiration, and other security issues.