Operations | Monitoring | ITSM | DevOps | Cloud

Not long ago, cloud cost was an engineering problem. FinOps teams owned it, finance leaned in occasionally, and everyone else stayed out of it. Now, that’s changed. AI changed who has skin in the game. CFOs get asked about it in board meetings. CEOs field questions on earnings calls. The audience for cloud cost management has exploded — and that means the conversation CloudZero is built to enable isn’t only a technical one, it’s a business one.

Have you noticed AI recently? Yeah, us too. Generative AI is wreaking havoc on the software status quo, and that includes licensing, and that generates … opinions. Sentry has a long history of having opinions about software licensing. We started life as an unlicensed side project in 2008, then went through BSD, to BSL, to writing our own license, FSL.

Technology leaders spent the past decade investing heavily in visibility. They expanded monitoring footprints, adopted cloud-native observability tools, integrated analytics dashboards, and layered on automation intended to streamline detection. Every addition promised deeper insight. Every initiative aimed to bring clarity to increasingly complex environments. Yet operations feel more chaotic, not less. Outages move faster. Incidents cross more boundaries. Signals appear without context.

Struggling with cloud complexity? Compare dedicated, partner, and IPsec connections to find the right private connectivity solution. Multicloud environments bring complexity, and how you connect to your CSPs can make or break performance, cost, and reliability. Here’s how dedicated, partner, and IPsec connections compare — and which might be right for your business. There are three main methods of connecting to the cloud with private connectivity.

Artificial intelligence recently took a major leap from “saying” to “doing.” Instead of simple back-and-forth chats, we’re now allowing automated AI processes to take action on our behalf—from responding to emails to building and deploying complete applications. This shift from “assistant” to “actor” can make applications more capable, but it also creates additional failure modes.

In the shift left era where it feels like we’re pushing everything as far to the start of the SDLC as we can, it may seem counterintuitive to shift anything right. That is, however, exactly what I suggest when it comes to generating metrics. How far you go to the right of the SDLC is a much more nuanced question and is dependent on a lot of factors, and on what metrics you’re talking about.

Teams continuously deploy programmable telemetry pipelines to production, without having access to a dry-run mode. At the same time, most organizations lack staging environments that resemble production – especially with regards to observability and other platform-level services.

For years, our annual State of Digital Operations report has been the industry benchmark for understanding how organizations manage incidents, build resilience, and evolve their operational practices. Each year, we survey hundreds of business and operations leaders worldwide to capture the challenges, priorities, and emerging practices shaping digital operations.

This blog is based on the webinar, “AI panel: The next wave of AI technology”. You can watch the full recording by clicking here! The pace of AI innovation is reshaping research, business, and everyday life. However, as breakthroughs in Large Language Models (LLMs) and high-performance computing accelerate, they bring new technical challenges around scale, efficiency, and reliability.

Coroot is an open source observability tool that uses eBPF to collect telemetry directly from applications and infrastructure. One of the things it does is capture L7 traffic from TLS connections without any code changes, by hooking into TLS libraries and syscalls. Works great for OpenSSL. Works for Go. Then rustls enters the picture and everything stops being obvious. With OpenSSL, everything is nicely wrapped: From eBPF’s point of view this is perfect: Everything happens inside one call.