Operations | Monitoring | ITSM | DevOps | Cloud

Are you thinking about switching from platform engineering to DevOps? You're not alone. In order to remain competitive, many organizations are making this crucial change as the world of software development and operations continues to change. This article will discuss the reasons behind the transition, what it implies, and most importantly, how your organization may successfully manage the change.

This month, Sysdig has released Process Tree which enriches the Events feed for workload-based events. This helps with identifying all the processes that led up to the offending process. This is in technical preview status. Sysdig has also released Sysdig Secure Live.

A containerized approach to software deployment means you can deploy at scale without having to worry about the configuration of each unit. In Kubernetes, clusters do the heavy lifting for you—they’re the pooled resources that run the pods that hold your individual containers. You can divide each cluster by namespace, which allows you to assign nodes (ie the machine resources in a cluster) to different roles or different teams. Resource quotas limit what each namespace can use.

In my previous blog post, I discussed how transitioning from legacy monolithic applications to microservices based applications running on Kubernetes brings a range of benefits, but that it also increases the application’s attack surface. I zoomed in on creating security policies to harden the distributed microservice application, but another key challenge this transition brings is observing and monitoring the workload communication and known and unknown security gaps.

Expenditure on cloud computing services reached a mammoth 225 billion dollars in 2022. Companies start their cloud-native journeys with the best intentions and consume the many benefits including: But current cloud expenditure growth levels are unsustainable for many organizations and with 82% of organizations investing in FinOps staff it shows that cloud expenditure is top of mind in the c-suite.

When Kubernetes components like nodes, pods, or containers change state—for example, if a pod transitions from pending to running—they automatically generate objects called events to document the change. Events provide key information about the health and status of your clusters—for example, they inform you if container creations are failing, or if pods are being rescheduled again and again. Monitoring these events can help you troubleshoot issues affecting your infrastructure.