Spot by NetApp’s Ocean continuously optimizes Kubernetes clusters with a wide feature-set tackling different aspects of running and managing Kubernetes containers in a cloud environment. One such aspect are the container resource requests defined in the cluster (upon which Ocean intelligently bin-packs pods on the underlying cloud VMs). Incorrect assumptions regarding the CPU and Memory required for an application, can incur unnecessary and costly cloud infrastructure waste.

In the modern era of digital businesses, web applications need to deliver on several grounds–performance, user experience, robustness, and scalability. However, many developers might agree that performance is of the utmost importance in any software application. The bells and whistles of a fancy UI and extensive functionalities can sometimes force performance to take the back seat. Additionally, there are a lot of reasons for performance to degrade over time.

In this blog, we will compare and contrast Falco vs. AuditD from a Host Intrusion Detection (HIDS) perspective. AuditD is a native feature to the Linux kernel that collects certain types of system activity to facilitate incident investigation. Falco is the CNCF open-source project for runtime threat detection for containers and Kubernetes. We will dig deeper into the technical details and cover the installation, detection, resource consumption, and integration between both products.

Providing breakthrough IT operations requires ITSM, DevOps, and other ITOps leaders to efficiently and economically deliver exceptional employee experiences and high-performing business applications. Achieving these expectations isn’t easy.

In a previous post, we explored the basic concepts behind using Grok patterns with Logstash to parse files. We saw how versatile this combo is and how it can be adapted to process almost anything we want to throw at it. But the first few times you use something, it can be hard to figure out how to configure for your specific use case.

IT Asset Management (ITAM) and IT Service Management (ITSM) are critical for any organization that requires IT capabilities to support business objectives. Both technologies provide IT operational support to an organization; however, the purpose and objectives of these technologies are quite different. Let’s explore the differences and similarities between ITAM and ITSM.

I’ve recently started working on a new project to build a Discord bot in Go, mostly as a way to learn more Go but also so I can use it to manage various things in Azure and potentially elsewhere. I figured it’d be useful to document some of this project to give some insights as to what I’ve done and why. First up was setting up the CI/CD pipeline for it so that I don’t need to worry about it later and can save myself a bunch of time when testing.

We recently announced a license change: Blog, FAQ. We posted some additional guidance on the license change this morning. I wanted to share why we had to make this change. This was an incredibly hard decision, especially with my background and history around Open Source. I take our responsibility very seriously. And to be clear, this change most likely has zero effect on you, our users. It has no effect on our customers that engage with us either in cloud or on premises.

This blog is the second in a two-part series and was adapted from The Enterprisers Project. At a time when CIOs can use cloud infrastructure to turn on new money-making services for customers overnight, how should we measure IT success? Hint: It's not about uptime. In part 1 of this series, we talked about how traditional IT metrics such as server capacity, I/O, utilization, and network throughput are less relevant today in our highly-digital world.

A significant portion of companies have vulnerabilities in their network management practices. These vulnerabilities include a lack of network visibility, configuration backups, proactive network planning, and up-to-date documentation. Despite these vulnerabilities, the majority of IT pros report high confidence in their networks, indicating a potential mismatch between perception and reality.