Operations | Monitoring | ITSM | DevOps | Cloud

AI is transforming how infrastructure and platform teams design, deploy, and operate systems. As organizations move from experimentation to production, a clear pattern is emerging. AI can decide what should change, but it cannot safely control how those changes are executed. This creates a gap in modern architectures. That gap is filled by a control plane. That control plane already exists in Puppet Enterprise Advanced.

For a decade, one idea has guided everything we’ve built at Tigera: How do you secure a dynamic system with a lot of moving parts that is changing rapidly, with a programmatic approach? Calico has applied that idea for Global 2000 companies running the largest Kubernetes platforms in the world, securing tens of millions of mission-critical transactions every day. Today I’m excited to announce the next chapter of that work: Lynx, a unified control plane for Kubernetes-native AI agents.

How many of your last five incidents were already sitting in the logs before anyone noticed? Most teams already collect more than enough log data. The problem starts with what happens next, and the same four gaps show up almost everywhere: This guide covers the log monitoring best practices that close those gaps. It walks through how to collect, structure, correlate, retain, and secure logs, so monitoring becomes a steady process and not a scramble during the next incident.

In an increasingly volatile job market, standing out from the competition is vital. For many in the open source community, formal recognition for self-taught skills is a significant challenge. These skills are often built through hands-on hobbies, side projects, and deep community contributions. While the market is flooded with certificates and certifications, most fail to reliably measure practical execution, or fall behind the rapid pace of industry changes.

The race to better AI-assisted observability has been a race for bigger and better models. But intelligence was never the real bottleneck. Structure and context were.

For years, vendor lock-in has been discussed as a theoretical risk. A concern to acknowledge in architecture reviews. A box to tick in compliance frameworks. A future problem that might need addressing. Our latest research reveals something more urgent. For UK organizations, lock-in isn't theoretical anymore. It's structural. It's measurable. And it's preventing organizations from acting on their own strategic priorities.

The CloudZero VS Code Extension 2.0 adds a sidebar that brings CostFormation namespace management directly into your editor, so you never have to break flow for a browser tab.

One of ActiveMQ's most powerful and underappreciated capabilities is its protocol polyglotism: a single broker can simultaneously accept Java JMS clients over OpenWire, Python services over AMQP, IoT sensors over MQTT, and Ruby scripts over STOMP, all routing messages between each other without protocol bridges or translation middleware.

The biggest cost in your business may not appear anywhere on your balance sheet because some of the most expensive problems are rarely measured directly. Lost productivity, recurring technology issues, underused applications, and the effort required to manage them all accumulate over time without ever appearing as a line item in a financial report.

When you work closely with Icinga Web 2, developing modules, building dashboards, poking around the internals, you naturally pick up on features that most users never think about. Some are usability improvements that deserve more attention than they get. Others are developer conveniences that turn out to be genuinely useful in the right user situation too. They’re just the kind of thing that rarely makes it into the getting-started guide. Not all of these will apply to your daily workflow.