Operations | Monitoring | ITSM | DevOps | Cloud

One of the great things about OpenTelemetry is that it’s a standard, and standards tend to proliferate. I was excited to see Claude Code add OpenTelemetry metric and log support in a recent release. What was really interesting—beyond the ability to capture usage data from Claude Code—is that you can also get pretty detailed logs about what you’re doing with Claude Code.

When someone leaves your organization, the first step IT usually takes is to disable their Microsoft 365 account. But have you ever stopped to ask: The answer might surprise you. If you’re not actively managing this, Microsoft will automatically delete that data — often in as little as 30 days. This post explains exactly what gets deleted (and when), why this is a problem, and what you can do to protect that data — without paying for unnecessary licenses.

Launching new enterprise software is one of the most strategic—but risk-laden—internal initiatives any organization can undertake. Done right, it accelerates transformation, streamlines operations, and boosts employee productivity. Done wrong, it can paralyze teams, spike IT tickets, and erode employee trust in the tools they’re given and the teams that support them.

Elephant flows are no longer rare. They’re foundational to AI workloads. In today’s GPU-heavy data centers, long-lived, high-volume flows can distort ECMP, overflow buffers, and rack up unexpected cloud bills. Kentik helps you see and tame these elephants with real-time flow analytics, automated alerting, and predictive capacity planning.

No business sets out to tolerate downtime. And yet, across industries, unexpected service disruptions continue to drain revenue, erode customer trust, and expose operational fragility. For CIOs and IT leaders, the real concern isn’t if systems will break, it’s whether your team can outpace the fallout. Because in a crisis, speed isn’t just an advantage it’s survival.

When your Go application moves beyond development, you need structured logging that persists. Writing logs to files gives you the control and reliability that stdout can't match, especially when you're debugging production issues or need to meet compliance requirements. This blog walks through the practical approaches, from Go's standard library to structured logging with popular packages.

Docker Swarm's logging model shifts from individual container logs to service-level aggregation. The docker service logs command batch-retrieves logs present at the time of execution, pulling data from all containers that belong to a service across your cluster. This approach gives you a unified view of distributed applications, but it comes with its patterns and considerations for effective observability.

Traditional IT process automation has always promised faster, more efficient operations. But for years, it’s been largely synonymous with service desk workflows: password resets, access requests, and the like. Those are important, no doubt. But limiting automation to the service desk is like only automating the assembly line in a factory while leaving the rest of the production floor manual.