Operations | Monitoring | ITSM | DevOps | Cloud

How context engineering creates production-ready agentic AI What if the AI strategy you spent the past year building is already being measured by a completely different set of rules? I recently joined Amy Machado, senior research manager at IDC and Jim Malone, senior contributing editor at CIO Marketing Services, for a webinar where we explored how buyer expectations, architectural requirements, and evaluation criteria are shifting as enterprises move from search-driven experiences to agentic AI.

As financial institutions move from AI experimentation to autonomous operations, trusted context, governance, and observability become the foundation for enterprise-scale Agentic AI. Artificial intelligence in financial services is entering a new era. Historically, financial services companies have focused on deploying generative AI to improve productivity, enhance customer experiences, accelerate software development, and streamline operations.

A recent IDC Spotlight report based on a survey of 685 public sector respondents found that 72% describe scaling AI from pilot to production as "very" or "somewhat" difficult.¹ Choosing the right model is only part of the challenge. Agencies also need to get their data ready for AI.

The new columnar metrics engine in Elastic Observability enables public sector IT teams to combine logging, metrics, and traces in one platform. As a result, SREs can improve uptime while protecting taxpayer dollars in the process. Public sector site reliability engineers (SREs) operate under a distinct set of pressures, whether that’s supporting a federal agency, a health department, a public university, or a transit authority.

How to build governance into autonomous security agents from the architecture up The industry has moved fast on capabilities. Agents now triage alerts, investigate endpoints, create detection rules, and enrich indicators, and they are even capable of performing most actions we as security operators can perform. The architecture patterns are maturing, as are the models, but governance is not keeping pace.

Incident response often depends on connecting two kinds of context: what changed in the environment and what the logs say happened next. Through a new integration with Elastic, Anyshift’s AI agent, Annie, can read from a customer’s Elasticsearch deployment to search logs, surface error and warning spikes, and correlate log evidence with infrastructure change history.

Gigamon COO Gareth Maclachlan on deep observability, the Elastic AI Ecosystem partnership, and AI traffic governance for security teams.

New research reveals why Australian businesses are entering the new financial year with bigger AI budgets and the same unsolved problem. One in three Australian businesses exceeded their AI budget last year. Yet, half of them plan to increase AI spending again this year. Yet the behaviour that caused those budget overruns remains largely unaddressed.

Making custom Elastic integrations better with both Automatic Import improvements and Integration Skills Elastic 9.4 shipped two tools for building custom integrations: Both are available today.

By benchmarking five GCP machine types across both Logstash and Kafka, LivePerson's observability team found that infrastructure selection (not just pipeline configuration) is one of the highest-leverage cost optimization decisions at scale.