Operations | Monitoring | ITSM | DevOps | Cloud

From infrastructure health to end-user experience.

For food and FMCG companies, managing freezers becomes more complex once equipment moves outside warehouses and company facilities. Freezers may be placed at supermarkets, retail stores, restaurants, distributors, convenience stores, and other customer locations, often across hundreds of cities or territories. At that scale, spreadsheets and manual field checks make it difficult to answer basic operational questions. Where is a particular freezer? Which outlet is responsible for it?

The secret sauce that powers Agentic Development Environments (ADEs) like Kepler is a little thing called the Agent Client Protocol (ACP). In this context, Kepler is the Client and harnesses like Claude Code and the Codex CLI are the Agents. We’re going to go over some of the details about how it works, how we use it at GitKraken, and how the protocol may be changing for the better.

Icinga Director’s CLI commands have supported import sources and sync rules for a long time, which includes listing, checking and running them. Before Icinga Director v1.11.6 two things you couldn’t do from the CLI, though, were narrowing a health check down to a single object, or deleting an import source or sync rule without opening the web UI. I’ll walk through both, using examples.

Why modernization is no longer optional - and how middleware holds the key to economics, resilience, and intelligent operations.

If your engineering teams run on ServiceNow, incidents are where they get work done. Putting cost work into an incident gives it the same path to resolution as any other work item your team handles. When a cost anomaly arrives as an incident, your teams route it, assign it, and resolve it on their usual SLAs. When a savings recommendation arrives as an incident, an engineer owns it and acts on it. Now you can send either straight into ServiceNow.

How do you resolve an outage your organization has no authority to fix? A managed database drops into read-only mode and stops accepting writes. There's no host to reach, no configuration file to edit, and no restart command available to your engineers. Cloud incident management begins at that boundary, where the response depends on a support channel and a provider status page. Plenty of what you already know still applies here.

A strong AI business case ties a specific goal to a measured outcome and a fully-loaded cost. Most fail because they skip one of the three: no clear mandate, an over-broad "AI fixes everything" scope, or a cost estimate that ignores adaptation and error-correction. Build it in six steps: define goals, identify uses, break work into tasks, evaluate models, assess total cost, then launch and refine. Most companies are now spending on AI. Far fewer can show what they got back.

Most teams can describe their GDPR obligations. Far fewer can produce the records that prove they met them. That gap is where GDPR compliance gets hard. The regulation reads as legal text, so it usually gets treated as legal work. About a third of it lands on the IT team instead: records of what you process, security controls that have to hold up, and deadlines measured in hours. Nobody asks for that evidence on a quiet week.

You shipped a skill. It worked. You closed the tab. That’s the whole problem. Model choice is a decision you make once, at the moment you’re least equipped to make it: before the skill is even authored. Then you never revisit it, because the skill stopped being interesting the day you got it working. So go back and check. Here’s how.