Operations | Monitoring | ITSM | DevOps | Cloud

Most cloud providers give you the hardware and leave you to figure out the rest. Civo AI is different. Chief Innovation Officer Josh Mesout explains how Civo thinks strategically about AI adoption, guiding organisations through the full lifecycle from planning and infrastructure through to running and scaling workloads, powered by best-in-class NVIDIA GPUs.

Anthropic have just released Sonnet 5, their cost effective alternative to Opus 4.8. The token cost is much lower, but when we analyse the telemetry, we find something surprising. It turns out, it's not all about token cost!

This workshop goes beyond the basics to show you how to monitor critical experiences in your application with workflows using dashboards, tracing, logs, and metrics.

There are a number of growing pains every business experiences, especially when that growth is hectic. And especially when there are so many moving parts in a business, things like licensing, rapid cloud spending, legacy applications, and tool sprawl may not be at the forefront of everyone’s mind.

Engineering teams are burning through AI budgets with nothing to show for it — $100M across 10,000 engineers and no cost per run, no cost per outcome, just a number that keeps climbing. When it runs dry, your infrastructure upgrade gets cut. Harness ties every AI token to the outcome it created: cost per run, cost per resolved ticket, and anomaly detection before the invoice hits. One customer went from a $28,000 black box bill to $0.60 per ticket.

At hyperscale, a regional cloud outage is not merely a technical disruption—for Samsung Account, which serves 2.1 billion users across three global regions, it is an immediate global service crisis. Fragmented, region-siloed monitoring creates blind spots that make early detection nearly impossible, leaving SRE teams perpetually reactive rather than predictive. The path to proactive reliability requires both a philosophical shift and a foundational change in how observability data is collected, unified, and reasoned over.

In the June edition of the Kubernetes Monitoring Helm chart office hours, we discuss the version 4.1 release, the upcoming 4.2 feature release, and we discuss the deprecation of the 1.x and 2.0 versions.

They look perfect together on paper, but the reality? Not so much. What do you think of this combo?