Operations | Monitoring | ITSM | DevOps | Cloud

Service desk leaders are being asked to do more with less. Ticket volumes keep climbing. SLAs keep tightening. Headcount rarely follows. Dashboards fill up fast, and before long, every conversation seems to start with a metric that’s in the red. Automation is pitched as the answer. But when it’s introduced only as a way to move faster or cut costs, it can backfire.

Redgate Flyway’s January update brings faster drift resolution, AI-powered deployment descriptions, and a look back at everything we shipped in 2025. Plus, we want to hear from you about how you’re managing database changes.

Earlier this year we launched Grafana Cloud Fleet Management to address the pain that comes with managing scores of telemetry collectors across departments and environments. We've been excited to see how organizations are using it to manage collectors at scale, but we've also heard from users who aren't sure how Fleet Management fits with their existing infrastructure-as-code tooling. The good news is Fleet Management is designed specifically to complement—not replace—tools like Terraform.

Setting up on-call is simpler than it seems. It comes down to a few clear decisions about your team and what your service actually needs. This guide walks you through those decisions. You’ll learn who to add in your rotation, how long shifts should last, when to hand off, and what coverage makes sense for your service. By the end, you’ll know exactly how to set up your first schedule and move from ad-hoc firefighting to organized incident response.

Some releases break new ground. Others clear the path. GitKraken Desktop 11.8 does both. You know that moment when you’re three commits deep into an interactive rebase and realize you’ve made a terrible mistake? Or when you’re trying to explain what changed on a feature branch, but it means manually selecting 47 commits? Or when you just want to preview a README without opening another app?

Let’s start with a question. What is DevOps all about? I’ll tell you my answer. In retrospect, I think the entire DevOps movement was a mighty, twenty year battle to achieve one thing: a single feedback loop connecting devs with prod. On those grounds, it failed. Not because software engineers weren’t good at their jobs, or didn’t care enough. It failed because the technology wasn’t good enough.

As the new year begins, development teams are looking to build momentum, set clear goals, and establish reliable, scalable processes that will help them deliver value consistently throughout 2026. That’s why many teams are turning to SQL Toolbelt Essentials: a powerful, easy-to-adopt toolkit that helps teams speed up database development, reduce risk, and standardize workflows.