Operations | Monitoring | ITSM | DevOps | Cloud

The latest News and Information on DevOps, CI/CD, Automation and related technologies.

DLP, Traffic Replay, and the Missing Link to Software Quality

In Part 1 and Part 2 we explored why testing modern software is so difficult. Production data is the most valuable input for testing, but it’s locked away because it contains PII and sensitive context. Traditional Synthetic Data Generation (SDG) was built for batch databases, not streaming systems. And AI coding agents amplify every weakness in existing test strategies because they need current, realistic data or they generate buggy code based on outdated assumptions.

How AI Coding Is Breaking Synthetic Data Generation

Traditional synthetic data generation approaches, still called “Test Data Management” (TDM) by legacy vendor, were designed for a world where applications were monolithic, databases were the center of gravity and change happened slowly. The world looks a lot different now. Modern systems are distributed, often times event-driven, and increasingly powered by streaming data and AI agents. In this environment, batch-oriented synthetic data generation fails to capture how systems actually behave.

Why Your Company Will Be Running OpenClaw Next Year

You’ve probably heard of OpenClaw. Maybe you’ve seen the demos where an AI agent opens a browser, navigates to your CRM, fills in a form, and files a support ticket. No API required. Maybe you thought “that’s cool but I’d never run that at work.” Your employees already are. According to Permiso’s research, 22% of enterprise customers have employees running OpenClaw without IT approval.

Syslog Checks: How to find Insights in the Data Flood

Every SysAdmin knows the feeling. They are swimming in logs—terabytes of them. Every daemon, service, and kernel subsystem religiously writing their activities to syslog. The data exists. The signals are there. Yet, somehow, incidents still are still unpredictable. How is this even possible? Here's why this happens: Traditional syslog infrastructure was designed for storage and retrieval, not detection and response.

How to Generate a New Puppet Module with VS Code and GitHub Copilot

Revolutionize your infrastructure by leveraging AI tooling in the Puppet ecosystem. In this technical demonstration, we explore how to significantly reduce the time required to create new Puppet modules using Visual Studio Code, GitHub Copilot, and the Puppet Model Context Protocol (MCP) server.

6 Underused Git Commands That Save Time

Git is full of underused powers that most developers never discover. In this GitKon 2025 session, GitKraken Senior Product Manager Jonathan Silva reveals 6 lesser-known Git commands that solve real workflow pain points, from recovering lost commits to managing stashes strategically. Learn how to undo commits without losing work, recover deleted branches with git reflog, cherry-pick without immediate commits, target specific stashes, see contributor breakdowns, and more. Jonathan also demonstrates how GitKraken Desktop makes these workflows visual and intuitive.

Follow-the-sun and other on-call models

Most teams run on-call using rotation-based schedules where responsibility shifts every few days or weeks. But some situations call for different models that change who responds based on time zones, expertise, or the type of incident that triggers. This guide walks you through six on-call models that work outside the standard rotation patterns.

5 Offbeat on-call rotations that work

Most teams choose standard on-call patterns like weekly or daily rotations. But sometimes a less conventional rotation can solve a specific problem or just fit better with how your team works. This guide walks you through five offbeat on-call rotations. For each, we look at why it might work for you and the challenges involved. This helps you see the full picture before you decide to try them out. Let’s dive in!