Operations | Monitoring | ITSM | DevOps | Cloud

Kubernetes has transformed how modern applications are deployed and scaled. Its flexibility and automation power innovation but also expand the attack surface. From control plane access to runtime drift, Kubernetes introduces layers of complexity that can obscure visibility if not properly monitored. For security leaders, Kubernetes is both an opportunity and a risk. While it enables agility, it also decentralizes security responsibility across teams, tools, and cloud layers.

Modern enterprises are generating more high-volume observability and security data than ever, which means the cost and complexity of getting analytics-ready data into Databricks are only growing. With the new Databricks Destination for Cribl Stream, organizations finally have a governed, scalable, and cost-efficient way to take full control of their data pipelines, accelerate AI-driven analytics, and unlock real business value from their Databricks investment.

If there was ever a year for AI observability, it was 2025. Vendors released assistants to cover a variety of use cases. Coralogix released the first agent (distinct from assistants!), Olly, an autonomous, multi-agent observability platform. The direction of travel is clear, but many vendors and users are about to run into some significant problems with their data layer.

Customer logs data is always messy. Being (and building!) an observability platform, we get to see all the beautiful, creative ways it can be messy, every single day. And yet, our customers expect, quite fairly, I might add, perfect query results and peak performance. Info SigNoz is an open-source observability platform that can be your one-stop solution for logs, metrics and traces.

If data centres were a country, they’d rank fifth in electricity consumption by 2026. Over the past few years, the resulting carbon footprint of the technology industry has sparked the fast-growing green software movement, led by the Green Software Foundation. How can we continue to innovate software in a way that also minimises its impact on the environment? This has been a fascinating problem I’ve been exploring for a few years now.

Security teams face a critical question: “What logs should we collect, and what detections should we enable to protect against threats targeting our industry?” For a bank in the northeast, this isn’t academic. Threat groups like FIN7, Lazarus Group, and Carbanak specifically target financial institutions with sophisticated attacks ranging from SWIFT compromise to ransomware.