Operations | Monitoring | ITSM | DevOps | Cloud

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

Policy-as-code vs. policy-as-documentation: The difference that matters

A documented policy only works if every engineer remembers it, every time, under deadline pressure. That's the gap policy-as-code closes. This video covers what that actually looks like in practice: The instructions don't change. What changes is whether something actually enforces them, or just hopes someone reads them.

How to Break Into Network Engineering With Network+ and No Prior Experience

Breaking into network engineering can feel difficult when every job posting seems to ask for experience you do not have yet. But experience does not always have to start with a full-time networking role. Certifications, hands-on labs, personal projects, and entry-level IT work can all help you build the foundation employers expect.

When login systems become an ops problem

SSO usually enters a company as a convenience project. People are tired of juggling passwords, new employees need access faster, and security wants fewer loose credentials floating around the business. At first, that sounds like a clean IT improvement. Then the company grows, tools multiply, teams work across more environments, and login becomes part of the operating layer that keeps the whole business moving.

SaaS Sprawl Is Becoming an IT Problem: Here's How to Bring It Under Control

For most organizations, SaaS sprawl does not begin with a bad technology decision. It starts with a useful tool. Marketing needs a new analytics platform. Sales adopts prospecting software. HR adds an applicant tracking system. Engineering signs up for another monitoring service. Someone discovers an AI tool that saves several hours a week and puts it on a company card. Each purchase makes sense on its own.

Incident Management: 20 Years of Change

Incident management fundamentals still apply, even as hybrid cloud and Kubernetes reshape incidents. Garrett Douglas joins LogicMonitor's Coffee and Context on why one failure floods ITOps with alerts and fuels alert fatigue. The bottleneck is incident context: knowing which alerts matter for incident response. Forrester's report Incident Management Has Outgrown Its Playbook frames context as the new competitive advantage.

AI is changing how organizations operate

AI is changing how organizations operate, but one thing has not changed: critical services cannot fail. Whether it is financial markets, healthcare, or other mission critical environments, organizations need observability that delivers value quickly, not weeks or months later. In this clip with theCube, Virtana CEO Paul Appleby explains how Virtana combines high fidelity telemetry with AI-driven intelligence to discover dependencies, correlate relationships, and deliver actionable insights within hours.

Surviving the uncharted: when dedicated OpenStack expertise is your best ally in disaster recovery

Some support cases are routine. Others take you off the documented path entirely, into territory where the only way forward is deep, hands on open source expertise. This series looks at how Canonical Support navigates the unexpected: cases where standard playbooks aren’t enough, and a support engineer helps a customer find a solution in real time. This is one of those cases.

How to Use Claude Code with CircleCI to Fix Failed Builds

Give Claude Code direct access to CircleCI and let it diagnose failed builds, fix issues, and keep iterating until your pipeline is green. In this tutorial, we walk through how to connect Claude Code to CircleCI using the CircleCI CLI. You’ll see how Claude can read pipeline results, identify test failures, make fixes, trigger new builds, and monitor CircleCI without leaving the terminal.

How to set up CircleCI with Cursor Origin

CircleCI now integrates with Cursor Origin, bringing scalable CI/CD to Origin-hosted repositories. In this demo, see how to connect an Origin repository to CircleCI, configure your pipeline triggers, run a build, and report CI status back to your Origin pull request. Already using CircleCI? Your existing.circleci/config.yml works as-is, with no Origin-specific CI syntax or separate config to maintain.