Operations | Monitoring | ITSM | DevOps | Cloud

How to automate artifact cleanup in Harness Artifact Registry without breaking production | Harness Blog

AI is changing artifact management in two ways at once. Every AI-generated pull request, dependency update, and automated build creates more container images, packages, and Helm charts than ever before. Registries are growing faster than engineering teams can manage them, driving up storage costs and leaving thousands of stale artifacts behind. At the same time, the cost of deleting the wrong artifact has never been higher.

The AI Hack Nobody Told You About

AI agents are now hacking on their own — and it already happened to two of the world's biggest AI labs. OpenAI's models broke out of a test sandbox, exploited a vulnerability, and hit Hugging Face's production systems. Days later, Anthropic reviewed over 141,000 evaluation runs and found three of its own Claude models had done the exact same thing to three different organizations.

Agent security starts with where the agent runs, not how it behaves

When engineering teams evaluate AI agents, the first questions are usually about capability. Which model performs best? How much faster can it write code? What's the return on investment? Security, if it enters the conversation at all, tends to come later. Patrick Dawkins, Principal Software Engineer at Upsun, thinks that's backward. Over the past year, he's been building the infrastructure that enables AI agents to operate safely within engineering teams.

Railway Mania, the birth of the S&P 500, and the lesson for the AI era

In 1846, Britain poured roughly 7% of its national income into railways, proportionally about three times what the U.S. spends on AI infrastructure today. The technology delivered everything it promised, and a generation of investors still lost their shirts. What sorted the winners from the wreckage wasn't conviction about the technology; it was whether ROI was measured or asserted. The man who fixed that problem gave his name to the S&P 500.

How SigNoz MCP Helped MSI Find 20 Unnecessary Operations

Taylor Mattison explains how SigNoz MCP helped surface wasted work inside MSI's sales-order workflow. Warning checks were firing on user actions that had nothing to do with any warning they could raise. By comparing telemetry across the workflow, Taylor could point to unnecessary operations that were wasting API calls, database time, and server capacity. This clip is part of our MSI customer story on using SigNoz MCP with Claude to debug slow sales orders across the stack.

Running LLM Workloads in Production: An Operations Playbook for Teams That Did Not Sign Up for This

Somewhere in the past two years, AI quietly became an operations problem. The proof of concept your product team shipped - a support-ticket summarizer, a natural-language search box, a code-review assistant - graduated into a production dependency, and now it pages you. The failure modes are unfamiliar: latency distributions with tails measured in tens of seconds, upstream providers that throttle without warning, costs that scale with user enthusiasm rather than infrastructure size, and outputs that can be wrong in ways a health check will never catch.

Why Responsible Technology Use Matters

Technology plays an integral role in our lives today. Technology is applied in communications, education, business, shopping, and various other tasks we undertake daily. The emergence of new forms of technology such as Artificial Intelligence, Cloud Computing, and IoT has made life more comfortable, but at the same time, they present challenges including privacy concerns, cyberattacks, and the spread of misinformation, among others.

Your AI agents don't need better models. They need the same context.

Everyone on the team has good coding agents. That is not what made the team fast. The shared repo, the shared docs, and a glossary nobody is allowed to drift from did more than any model choice. In this Product Highlights conversation, Patrick Dawkins, a principal engineer at Upsun who is building Upsun Dispatch under a hard deadline, explains what his team changed to sustain that pace. His take: "As well as the team all having access to the same things and the same vocabulary, all the agents also have access to those docs.".

Spend More Time Talking to Humans

A few months ago, I noticed something happening. I would spend all day working with LLMs—prompting them, reviewing their work, and correcting them—and when I wasn’t working on my own code, I was reviewing LLM-generated code. By the end of the day, I was exhausted. This was a very unusual thing for me: I’ve been a software developer at startups for 30 years, and while sometimes I might have gotten stressed out, I had never been exhausted by the actual act of writing code.