The conventional wisdom in our industry says that AI demands a new operating model and specific data tailored for it. I disagree. AI is changing the rules, but not in the way people think ...
Most organizations invest heavily in security tools, policies, and controls. Yet despite these efforts, one reality persists: employees often find ways around them. This isn't always malicious. In many cases, it’s a response to friction, urgency, or misalignment between how work actually happens and how systems are designed to protect it. When employees bypass security, it creates blind spots. Sensitive data may move through unmonitored channels, access controls may be weakened, and risks that security teams intended to mitigate reappear in new forms ...
AI agents and agentic browsers now make up a growing share of the traffic reaching websites and applications. They search, compare, sign up, and increasingly complete purchases on behalf of the people who delegate those tasks. Digital experience monitoring (DEM) was built on the assumption that every session is performed by a person. That assumption no longer holds, and the measurements built on it are shifting without notice ...
IT operations teams dedicate an enormous amount of energy to tracking performance metrics. We spend our days staring at telemetry dashboards monitoring packet loss, jitter, latency spikes, and server utilization. We treat response times as the ultimate badges of honor. Yet after years of collaborating with enterprise network leaders, I have arrived at a simple truth. Users rarely evaluate IT based on network throughput or CPU graphs. They measure us on confidence ...
Enterprise networks were designed in an era when applications were predictable. They ran in centralized data centers, served relatively stable user bases, and operated within well-defined boundaries ... Today's applications look very different. They are cloud-native, distributed across regions, accessed by users from anywhere, and often rely on real-time data exchange. Yet many enterprise networks still reflect assumptions from an earlier generation. This mismatch is becoming increasingly visible ...
For decades, traditional observability tools have forced IT professionals to sift through endless dashboards, turning a flood of alerts into actionable insight and driving widespread burnout. While enterprises adopted AI to eliminate this friction, most still deploy it reactively rather than proactively ... As systems become more complex and IT moves to the center of business strategy, a reactive posture is unsustainable ...
Everyone wants to talk about models. Compute clusters. Benchmark scores that climb a fraction of a point and make headlines anyway. It's an easy conversation to have because it's measurable. But it's also increasingly beside the point ...
Most enterprise IT leaders can tell you exactly how many applications are running across their organization. They can surface a dashboard showing telecom spend by region, pull a report on SaaS license utilization, or call up a real-time view of mobile device inventory. The data is there, and IT leaders have largely delivered on the promise of visibility. Yet, in most organizations, that visibility has not translated into business value ...
When an application team reports that a service is slow, and a platform team confirms that the cluster is healthy, both statements can be true at the same time. The application team is describing response times observed in the code. The platform team is describing node, pod, and resource level conditions. Neither statement is incorrect. They are simply describing different layers of the same system, using different data. This is not primarily a matter of tooling. It is a difference in vocabulary, and it is one of the more common patterns in organizations running Kubernetes at scale ...
Traditional observability practices were not designed for systems that reason probabilistically, interact autonomously, and continuously evolve. With the rise of agentic AI, observability needs to evolve beyond just an operational monitoring discipline into a more strategic layer for governance and accountability across infrastructure, applications, workflows, and autonomous action ...
AI observability is quickly becoming its own technology category. That makes sense. Large language models and agentic AI introduce behaviors, dependencies and failure modes that traditional applications simply did not have. But there is a risk in treating AI observability as something completely separate from the rest of IT operations. AI may be new. The operational challenge underneath it is not ...
The most dangerous assumption in modern enterprise IT is that visibility comes automatically with more data collection. Network operations have followed a basic mechanics loop for years: detection, alerting, ticketing, and remediation, with success determined by MTTR. Now that stacks span multiple clouds, dozens of microservices, and a growing list of external SaaS dependencies you don't control, that reactive strategy has lost all effectiveness. The problem isn't a lack of infrastructure data. It's that teams are completely overwhelmed by the sheer volume of telemetry ...
For years, ITAM (IT Asset Management) teams' jobs were straightforward: track technology assets, maintain compliance, and optimize software investments. Today, those boundaries have blurred. As organizations navigate increasingly complex technology environments alongside the rapid rise of AI, ITAM has evolved from an operational function into a strategic discipline that helps organizations govern technology across the enterprise. The question facing organizations is no longer how to manage technology assets, but who should own them ...
Performance bottlenecks aren't uncommon when it comes to rolling out new technology, regardless of how capable or game-changing that technology might be. Every generation of new tech has encountered roadblocks that had to be overcome before it was truly able to shine. Virtualization forced organizations to rethink resource allocation, cloud transformation had us shift our focus toward scalability and elasticity, and microservices introduced entirely new challenges around observability and distributed systems. There's something different about AI, however ...
Consider a single order represented across order-management, execution, and settlement systems. Each database, message broker, and application may be online and processing its own records correctly. Yet the workflow has failed if related events arrive on different clocks, rely on inconsistent state, or cannot be reconciled before an operational decision must be made ...
AI now exists in almost every IT workflow. In a recent survey of more than 800 IT service professionals, all respondents indicated the use of AI in some form within their organization. But there's a growing paradox: if dashboards are clearing faster and alerts are resolved at unprecedented speed, why aren't IT service desks reporting lighter workloads? The research found that 71% of IT teams said their actual workload has remained flat or increased since adopting AI. This reality appears to contradict what we’ve been told about AI ...
Two things happened to production incidents between 2023 and now, and they did not happen at the same speed. The first is that a class of dependency that barely existed three years ago now accounts for one incident in ten. Incidents disclosed by AI model and AI application providers rose from 1.7% of all disclosed unplanned incidents in 2023 to 10.7% in 2026 year to date, roughly a sixfold rise; that counts only incidents at AI companies themselves, so the true share is higher. The second is that the time to close an incident has not come down ...
When an AI assistant gives an incomplete or incorrect answer, teams often blame the model. They adjust prompts, switch models, increase context windows or test a new retrieval strategy. However the model may not be a problem. In many enterprise AI workflows, the problem begins inside the document-ingestion pipeline ...
If you talk to any security or observability teams right now, they're all fighting the same fire: their tooling was built to ingest X, but their sources are pumping Y and soon to be doing Z. The knee-jerk reaction is always the same: we need more platform. However, this reaction is wrong. Let me explain why, because the solution to this problem is foundational, not financial. Instead of hurling yet more money at the problem, make sure you've done what's needed upstream ...
Enterprise AI often lacks governed access to where business processes actually execute. Without that access, AI agents may be able to reason, but they cannot operate reliably across enterprise workflows. For AI agents to effectively carry out workflows, they will require integration-layer context and controls. Organizations can implement these prerequisites by providing AI with managed access to the middleware layer ...