Once upon a time, in a tech company, an engineering team had the freedom to independently deploy updates and new features to a Kubernetes cluster. This autonomy helped speed up development but also led to unforeseen issues with resource management. The platform team responsible for maintaining the cluster's health noticed an increase in orphaned Persistent Volumes (PV), a piece of plug-in storage independent of other Kubernetes cluster pods.

If you’re in banking, you know the drill. Adhering to stringent EU regulations is a standard practice. This involves undergoing extensive audits, closely managing IT assets, maintaining your CIA (Confidentiality, Integrity, Availability) rating, conducting and responding to fire drills, and establishing continuity plans. So far, nothing new, and if you’re in other highly regulated environments, you know that these measures are commonplace.

ZenOps and StackState announce a partnership for the distribution in France of StackState solutions for Kubernetes problem detection and resolution, observability of containerized environments and application performance management. ZenOps will be able to offer these solutions to enterprises and the public sector, drawing on its technical expertise in cloud-native approaches and providing first-level support.

As Kubernetes adoption continues to surge across various industries, the need for robust monitoring solutions is more critical than ever. Effective Kubernetes monitoring not only ensures the health and performance of your containerized applications but also provides valuable insights for troubleshooting and optimizing your infrastructure. However, Kubernetes's distributed and dynamic nature presents unique challenges regarding monitoring and observability.

When Google Cloud welcomed StackState to offer our full-stack observability solution to their network of customers, we were thrilled. Our excitement only grew when Google invited us to join other partners this week at Google Cloud Next ’24 at the Mandalay Bay Convention Center in Las Vegas.

As a manager, figuring out how to talk to your engineering teams about building a strong observability strategy can feel overwhelming. But don't worry! This post will help you navigate the challenges to unlock the full power of observability in your IT environment. Drawing on insights from over 40 discussions with larger enterprises, we've put together a strategy assessment that examines three key focus areas — what we’re calling aspects — each encompassing three actionable steps.

StackState had a blast at this year's KubeCon + CloudNativeCon gathering in Paris! The discussions were in-depth, covering a wide array of topics and lasting much longer than in the past. This year, attendees seemed to have a considerably deeper understanding of the cloud-native ecosystem, probably attributed to its rapid growth. We also noticed a pretty dramatic evolutionary shift in the vendors at the expo hall, who were showcasing some truly progressive specialized solutions.

In one of our latest posts, StackState Co-Founder Mark Bakker described how eBPF revolutionizes observability and how StackState’s agents rely heavily on eBPF to capture and analyze the data moving through your cluster. Today, we’re looking at an example where our eBPF code failed and — by diving deep into the intricacies of eBPF implementation in the Linux kernel — share the tale of how we fixed it using even more eBPF.