Operations | Monitoring | ITSM | DevOps | Cloud

Kubernetes has been around for nearly 10 years now. In the past five years, we’ve seen a drastic increase in adoption by engineering teams of all sizes. The promise of standardization of deployments and scaling across different types of applications, from static websites to full-blown microservice solutions, has fueled this sharp increase.

Predictive maintenance is a maintenance strategy that uses machine learning algorithms trained with Industrial Internet of Things (IIoT) data to make predictions about future outcomes, such as determining the likelihood of equipment and machinery breaking down. Using a combination of data, statistics, machine learning and modeling, predictive maintenance is able to optimize when and how to execute maintenance on industrial machine assets.

Metrics are closely associated with cloud infrastructure monitoring or application performance monitoring – we monitor metrics like infrastructure CPU and request latency to understand how our services are responding to changes in the system, which is a good way to surface new production issues. As many teams transition to observability, collecting metric data isn’t enough.

1. Why use ilert with Pandora FMS? 2. ilert setup with Pandora FMS 3. How are ilert alerts shown? 4. Advanced ilert use: event correlation with Pandora FMS.

In our first blog post, we introduced the concept of cloud unit economics—a system to measure cost and usage metrics. It helps maximize cloud value for better outcomes per dollar spent. We reviewed what cloud unit economics is, why it’s crucial to FinOps success, and how it enables organizations to unlock the full business value potential of cloud computing.

What are the current options to migrate from OpenSearch to Elasticsearch®? OpenSearch is a fork of Elasticsearch 7.10 that has diverged quite a bit from itself lately, resulting in a different set of features and also different performance, as this benchmark shows (hint: it’s currently much slower than Elasticsearch).

We are introducing a new Snooze option for items. When Snoozing an item, the user will define how long an item will stop sending notifications for - once that time period expires then the item will return to normal and begin sending notifications again. Currently, setting an Item to have a status of Muted prevents notifications from being sent until somebody changes the status back to Active.

Many DevOps teams work proactively to meet security and compliance standards. They consider security best practices when developing software with open source components, scanning code for vulnerabilities, deploying changes, and maintaining applications and infrastructure. Security is a key feature of many of the tools they’re using, and the policies and industry standards they’re following.

According to the latest Crowdstrike report, in 2022 cloud-based exploitation increased by 95%, and there was an average eCrime breakout time of 84 minutes. Just as significantly, in 2021, the Biden administration passed an executive order to improve the nation’s cybersecurity standards. There are also upcoming laws like DORA in the European Union. So, increased cyber attacks and legislative pressures mean you need to (a) actively protect against threats and (b) prove that you are doing so.

In a recent reddit thread, I got into a conversation about justifying the cost of observability. It got to a really basic question about running a tech company: how do you know that any cost is justified? While a small number of expenses have clear and direct business values, a bunch of other costs, I would even say most costs, just aren’t that clear cut.