Operations | Monitoring | ITSM | DevOps | Cloud

Your AI coding agent can refactor a module, write tests, and open a PR. It can read your codebase, understand your patterns, and suggest changes that follow your conventions. What it cannot do, unless you set it up, is see what is actually happening in production. That is a problem. The agent that writes the code should have access to the errors, traces, and performance data that code generates once it ships. Without production context, your agent is writing fixes based on the code alone.

TL;DR OpenSearch 3.6 makes agentic search production-ready, with the AI-powered Launchpad provisioning full search apps in minutes and faster default vector search, and it's the first LTS release, bringing 18+ months of guaranteed support, SBOMs, and an upstream-first commitment (every fix goes back to the main project) so teams get fast-moving open source and a stable, supported platform at once.

Ticket deflection is the metric IT leaders point to when they talk about AI chatbot ROI, and the knowledge base is the part of the equation that determines whether that number moves. A chatbot can run natural language processing well and still deflect almost nothing if the content behind it is thin, outdated, or scattered across articles that don't match how people actually ask questions.

AI applications generate far more than model outputs. Every request includes prompts, retrieval, tool calls, agent steps, latency, token usage, and evaluation signals that all contribute to the final response. When something goes wrong, engineering teams need to understand what happened, why it happened, what it cost, and whether the outcome met quality expectations.

Monitoring tells you when an event you predicted has actually happened. Observability lets you investigate behavior you may not have predicted at all. For most of the past decade, that distinction was something teams could afford to treat as a philosophical debate, because their systems failed in expected ways that had been seen before. A memory leak, a bad deploy, a saturated connection pool. You could build a dashboard and alerts for each and sleep reasonably well.

In some organizations, high token counts have become a proxy for productivity. Some engineering teams are being pushed to max out context windows and wire in sprawling tool sets. More tokens can mean better agent reasoning and richer context during development, but token costs compound in production. Tokens accumulate across sessions, users, and tool calls in ways that are easy to overlook. Datadog’s 2026 State of AI Engineering report quantifies the scale of this problem.