Operations | Monitoring | ITSM | DevOps | Cloud

Today, I’m very happy to share a new report, Bridging the AI Acceleration Gap, from Harvard Business Review Analytic Services and sponsored by Nexthink. It examines how employee-led AI adoption is reshaping the role of IT—and what technology leaders need to do next.

Your code review tool does more than display diffs. It shapes how your team shares knowledge, catches bugs, and ships software. With AI-generated code accelerating PR volume, choosing the right code review platform is a decision that directly affects your team’s velocity. GitKraken connects PR workflows, multi-repo management, and AI-assisted review into a single developer experience platform.

Starting an experiment with an LLM has never been easier. Keeping a growing collection of those experiments consistent is another matter. Earlier this year, as more teams began exploring AI features here at Grafana Labs, we repeatedly encountered the same pattern: a new experiment would start, move quickly, and build its own client for whichever model provider it needed. The next experiment would do the same, with a slightly different abstraction for streaming, tools, errors, or provider configuration.

Why does a ClickHouse cluster report every node as healthy while inserts start failing and dashboards go stale? Most often the failing subsystem was never represented in the metrics anyone had on screen. A node answers its health check while its replication queue has been growing for hours. ClickHouse breaks in specific, repeatable ways. Parts accumulate faster than background merges can consolidate them. Coordination drops quorum and every replicated table quietly turns read-only.

How many backup jobs completed successfully in your environment last night, and how many of those systems could you bring back inside the window the business agreed to? Most backup consoles answer the first question well. They report job status, completion time and volume written, then roll it into a reassuring compliance summary. The second question needs different evidence, usually missing from that screen. The distance between those answers shows up during the recovery attempt.

There are many conversations about the use of AI, particularly how engineering teams are using it in their coding workflows. Manual work is being replaced by agent-driven automation, and human value increasingly lies in the higher-order work: writing specs, thinking through architecture, steering the direction, exercising taste, and reviewing the output.

If your company runs on Google Workspace, your team lives in Google Chat. That is where the standup happens and where threads turn into decisions. Cost alerts can now go there too. This is relevant because an alert only does something if it reaches people in a place where they can talk about it. Email is great for a record but not great for a reaction. An anomaly notification sitting in an inbox waits for that person to open it, decide it is real, and then go tell everybody else.

The OpenTelemetry Operator changed how teams approach telemetry collection in Kubernetes. The core appeal of zero-code instrumentation is that you can bring up telemetry inside application containers to collect traces, metrics, and logs without touching your source code or rebuilding your container images. However, if you follow the default OpenTelemetry Operator documentation, you quickly run into a heavy operational prerequisite: the Instrumentation CRD.