Skip to main content

OllyGarden Extends AI Agent to Identify Instrumentation Gaps

OllyGarden this week revealed it has extended the capabilities of its artificial intelligence (AI) for optimizing the collection of telemetry data to now also discover where no existing instrumentation exists and what instrumentation should be applied to address that gap.

Fresh off raising an additional $4 million in funding, OllyGarden founder Juraci Paixão Kröhling said a Minimum Viable Instrumentation (MVI) capability that has been added to the Rose AI agent the company previously developed makes it possible to identify the most relevant sources of telemetry data that should be instrumented using OpenTelemetry, an open-source framework for collecting that data that is being advanced under the auspices of the Cloud Native Computing Foundation (CNCF).

That capability extends the scope of an AI agent that was created to help DevOps teams reduce the amount of telemetry data they need to collect and store by identifying which logs, traces and metrics are the most relevant. The overall goal is to reduce the massive amount of telemetry data that DevOps teams would need to collect, analyze and store, said Paixão Kröhling.

The amount of telemetry data being collected naturally varies from one DevOps team to the next, but as more AI workloads are deployed the volume of that data continues to steadily rise. Aggregating all that data in a way that enables IT environments to be observed is quickly becoming cost-prohibitive for many DevOps teams.

The overall goal is to make it simpler for DevOps teams to calibrate the exact amount of telemetry data they need to observe an IT environment to ultimately reduce the overall level of noise that prevents meaningful signals from being fully understood, said Paixão Kröhling.

Specifically, the Rose AI agent continuously evaluates the quality of the telemetry data being collected, identifies issues, and then generates source-level fixes that DevOps teams can then apply. That approach prevents bad or irrelevant telemetry data from ever reaching a backend observability platform in the first place, noted Paixão Kröhling. Over the past year, OllyGarden claims to have helped DevOps teams identify opportunities to reduce telemetry data volume across up to 85% of their logs.

In theory, observability platforms will play a crucial role in enabling DevOps teams to embed AI agents within their workflows by providing them with access to telemetry data they can reason across. The issue is finding a way to reduce the volume of data being exposed to them to ensure those AI agents generate higher-quality outcomes at the lowest cost possible. Otherwise, DevOps teams are likely to discover that the cost of deploying AI agents will far exceed their available budgets.

It may be a while yet before most DevOps teams will be pervasively deploying fully autonomous AI agents across production environments, but at this juncture it’s more a question of when and to what degree than it is if. The fundamental challenge is first ensuring that AI agents are not reasoning across irrelevant data and then finding a way to validate the output they provide. Only then are DevOps teams going to trust AI agents enough to execute tasks with little to no supervision. Until then, AI agents that, by definition, are probabilistic will be relegated to performing tasks that, while reducing toil for DevOps engineers, still need to be closely monitored and verified at almost every step of highly deterministic DevOps workflows.



from DevOps.com https://ift.tt/dlqG7Z6

Comments

Popular posts from this blog

One Year Later: How U.S. Winemakers Averted Disaster

One Year Later: How U.S. Winemakers Averted Disaster By Eric Asimov from NYT Food https://ift.tt/32fgBqf Wines, Shutdowns (Institutional), Layoffs and Job Reductions, Quarantine (Life and Culture)

The Agent Failure Your Approval Gate Can’t Catch

An agent that does the wrong thing leaves evidence — a bad diff, a malformed record, a customer complaint. An agent that does nothing and reports success leaves a green checkmark, and green is the one signal your incident process is built to trust. Worry more about the second failure, because everything a DevOps team owns for catching failure — exit codes, run status, alert rules, the dashboard itself — is instrumentation built for software that fails loudly. None of it fires when the failure is an absence. Andrew Filev made the strongest version of the reliability argument in these pages in July ( https://devops.com/reliability-comes-from-the-system-not-the-agent/ ): reliability is a property of the system, not the agent. “Reliability has rarely come from any single component in isolation,” he wrote. “It comes from how systems handle failure.” Aviation does not assume perfect pilots and hospitals do not assume perfect surgeons; both wrap imperfect actors in app...

Future Proofing the Foundation for AI-Ready Security Operations

Last December, the International Telecommunication Union (ITU), the United Nations’ (UN) body for information and communication technologies, supported  Open Cybersecurity Schema Framework (OCSF)  for ratification as an international standard by June 2026. Standardization is now a global necessity as governments worldwide integrate ITU standards into their national cybersecurity policies. First, What is OCSF? The OCSF provides a standardized approach to streamline security operations, improve threat detection, and accelerate incident response. This unlocks the full potential of security data. A standardized schema for security events normalizes data from various sources, which creates a unified foundation for advanced analytics and AI-powered tools. This standardization is crucial for unleashing the full potential of generative AI in cybersecurity, allowing organizations to better identify patterns and correlations across disparate data sources. Data Standardiza...