Skip to main content

RapDev Launches Arlo

RapDev announced the latest extension of Arlo, its suite of AI Agents, for Datadog environments - built to streamline observability workflows, reduce operational toil, and accelerate incident resolution.

Launching late Q2 on the Datadog Marketplace, Arlo leverages RapDev's deep engineering expertise to deliver proactive AI-driven solutions that automate investigation and troubleshooting of incidents in real-time, using several LLM techniques. Arlo empowers SREs and engineering teams to stay focused on innovation, avoiding manual troubleshooting and infrastructure noise.

By embedding prompt-chaining techniques directly into Datadog environments, Arlo delivers real-time diagnostics, actionable remediation, and autonomous response capabilities, making incident resolution both faster and smarter.

Each Arlo Agent targets a specific area of infrastructure or application health, offering measurable outcomes and fast time-to-value:

  • Arlo for Linux: Flags disk space issues, identifies large or runaway log files, and initiates cleanup actions before business services are impacted.
  • Arlo for Kubernetes: Surfaces saturation and deployment anomalies at the node level, with built-in recommendations to reduce drift and prevent future failure.
  • Arlo for Windows: Identifies memory pressure and system constraints on Windows VMs hosting .NET applications, pinpointing exactly which processes to address.
  • Arlo for Networking: Diagnoses spanning tree and switch-level issues by logging into network devices and identifying misconfigurations, cutting network troubleshooting time dramatically.

"Arlo takes the burden off engineers by running real troubleshooting workflows across Linux, Windows, Kubernetes, and network devices," said Jay Barker, Director of Datadog Engineering at RapDev. "Whether it's root cause analysis or live remediation, Arlo accelerates incident response and turns SRE hours into minutes - all within your existing Datadog environment."

Whether investigating root causes, recommending fixes, or running commands directly, Arlo acts as a digital teammate that never sleeps - automating repetitive diagnostics so teams can resolve issues with confidence and speed.

"Arlo is built for the next wave of ProdOps," said Tameem Hourani, Principal and Founder at RapDev. "With agents that act directly within your observability workflows, it's not just surfacing data - it's taking action. That's where our industry is headed: AI agents that troubleshoot, resolve, and never sleep, so your teams can."

Arlo for Datadog exemplifies RapDev's commitment to building AI-native solutions that enhance core platform capabilities, improve engineer productivity, and deliver operational efficiencies at scale.

Arlo's launch marks a significant milestone in RapDev's AI strategy, with additional agent capabilities and customer-driven enhancements already in development.

The Latest

For years, production operations teams have treated alert fatigue as a quality-of-life problem: something that makes on-call rotations miserable but isn't considered a direct contributor to outages. That framing doesn't capture how these systems fail, and we now have data to show why. More importantly, it's now clear alert fatigue is a symptom of a deeper issue: production systems have outgrown the current operational approaches ...

I was on a customer call last fall when an enterprise architect said something I haven't been able to shake. Her team had just spent four months trying to swap one AI vendor for another. The original plan said three weeks. "We didn't switch vendors," she told me. "We rebuilt half our integrations and discovered what we'd actually been depending on." Most enterprise leaders don't expect that to be the experience ...

Ask any senior SRE or platform engineer what keeps them up at night, and the answer probably isn't the monitoring tool — it's the data feeding it. The proliferation of APM, observability, and AIOps platforms has created a telemetry sprawl problem that most teams manage reactively rather than architect proactively. Metrics are going to one platform. Traces routed somewhere else. Logs duplicated across multiple backends because nobody wants to be caught without them when something breaks. Every redundant stream costs money ...

80% of respondents agree that the IT role is shifting from operators to orchestrators, according to the 2026 IT Trends Report: The Human Side of Autonomous IT from SolarWinds ...

40% of organizations deploying AI will implement dedicated AI observability tools by 2028 to monitor model performance, bias and outputs, according to Gartner ...

Until AI-powered engineering tools have live visibility of how code behaves at runtime, they cannot be trusted to autonomously ensure reliable systems, according to the State of AI-Powered Engineering Report 2026 report from Lightrun. The report reveals that a major volume of manual work is required when AI-generated code is deployed: 43% of AI-generated code requires manual debugging in production, even after passing QA or staging tests. Furthermore, an average of three manual redeploy cycles are required to verify a single AI-suggested code fix in production ...

Many organizations describe AI as strategic, but they do not manage it strategically. When AI plans are disconnected from strategy, detached from organizational learning, and protected from serious assumptions testing, the problem is no longer technical immaturity; it is a failure of management discipline ... Executives too often tell organizations to "use AI" before they define what AI is supposed to change. The problem deepens in organizations where strategy isn't well articulated in the first place ...

Across the enterprise technology landscape, a quiet crisis is playing out. Organizations have run hundreds, sometimes thousands, of generative AI pilots. Leadership has celebrated the proof of concept (POCs) ... Industry experience points to a sobering reality: only 5-10% of AI POCs that progress to the pilot stage successfully reach scaled production. The remaining 90% fail because the enterprise environment around them was never ready to absorb them, not the AI models ...

Today's modern systems are not what they once were. Organizations now rely on distributed systems, event-driven workflows, hybrid and multi-cloud environments and continuous delivery pipelines. While each adds flexibility, it also introduces new, often invisible failures. Development speed is no longer the primary bottleneck of innovation. Reliability is ...

Seeing is believing, or in this case, seeing is understanding, according to New Relic's 2025 Observability Forecast for Retail and eCommerce report. Retailers who want to provide exceptional customer experiences while improving IT operations efficiency are leaning on observability ... Here are five key takeaways from the report ...

RapDev Launches Arlo

RapDev announced the latest extension of Arlo, its suite of AI Agents, for Datadog environments - built to streamline observability workflows, reduce operational toil, and accelerate incident resolution.

Launching late Q2 on the Datadog Marketplace, Arlo leverages RapDev's deep engineering expertise to deliver proactive AI-driven solutions that automate investigation and troubleshooting of incidents in real-time, using several LLM techniques. Arlo empowers SREs and engineering teams to stay focused on innovation, avoiding manual troubleshooting and infrastructure noise.

By embedding prompt-chaining techniques directly into Datadog environments, Arlo delivers real-time diagnostics, actionable remediation, and autonomous response capabilities, making incident resolution both faster and smarter.

Each Arlo Agent targets a specific area of infrastructure or application health, offering measurable outcomes and fast time-to-value:

  • Arlo for Linux: Flags disk space issues, identifies large or runaway log files, and initiates cleanup actions before business services are impacted.
  • Arlo for Kubernetes: Surfaces saturation and deployment anomalies at the node level, with built-in recommendations to reduce drift and prevent future failure.
  • Arlo for Windows: Identifies memory pressure and system constraints on Windows VMs hosting .NET applications, pinpointing exactly which processes to address.
  • Arlo for Networking: Diagnoses spanning tree and switch-level issues by logging into network devices and identifying misconfigurations, cutting network troubleshooting time dramatically.

"Arlo takes the burden off engineers by running real troubleshooting workflows across Linux, Windows, Kubernetes, and network devices," said Jay Barker, Director of Datadog Engineering at RapDev. "Whether it's root cause analysis or live remediation, Arlo accelerates incident response and turns SRE hours into minutes - all within your existing Datadog environment."

Whether investigating root causes, recommending fixes, or running commands directly, Arlo acts as a digital teammate that never sleeps - automating repetitive diagnostics so teams can resolve issues with confidence and speed.

"Arlo is built for the next wave of ProdOps," said Tameem Hourani, Principal and Founder at RapDev. "With agents that act directly within your observability workflows, it's not just surfacing data - it's taking action. That's where our industry is headed: AI agents that troubleshoot, resolve, and never sleep, so your teams can."

Arlo for Datadog exemplifies RapDev's commitment to building AI-native solutions that enhance core platform capabilities, improve engineer productivity, and deliver operational efficiencies at scale.

Arlo's launch marks a significant milestone in RapDev's AI strategy, with additional agent capabilities and customer-driven enhancements already in development.

The Latest

For years, production operations teams have treated alert fatigue as a quality-of-life problem: something that makes on-call rotations miserable but isn't considered a direct contributor to outages. That framing doesn't capture how these systems fail, and we now have data to show why. More importantly, it's now clear alert fatigue is a symptom of a deeper issue: production systems have outgrown the current operational approaches ...

I was on a customer call last fall when an enterprise architect said something I haven't been able to shake. Her team had just spent four months trying to swap one AI vendor for another. The original plan said three weeks. "We didn't switch vendors," she told me. "We rebuilt half our integrations and discovered what we'd actually been depending on." Most enterprise leaders don't expect that to be the experience ...

Ask any senior SRE or platform engineer what keeps them up at night, and the answer probably isn't the monitoring tool — it's the data feeding it. The proliferation of APM, observability, and AIOps platforms has created a telemetry sprawl problem that most teams manage reactively rather than architect proactively. Metrics are going to one platform. Traces routed somewhere else. Logs duplicated across multiple backends because nobody wants to be caught without them when something breaks. Every redundant stream costs money ...

80% of respondents agree that the IT role is shifting from operators to orchestrators, according to the 2026 IT Trends Report: The Human Side of Autonomous IT from SolarWinds ...

40% of organizations deploying AI will implement dedicated AI observability tools by 2028 to monitor model performance, bias and outputs, according to Gartner ...

Until AI-powered engineering tools have live visibility of how code behaves at runtime, they cannot be trusted to autonomously ensure reliable systems, according to the State of AI-Powered Engineering Report 2026 report from Lightrun. The report reveals that a major volume of manual work is required when AI-generated code is deployed: 43% of AI-generated code requires manual debugging in production, even after passing QA or staging tests. Furthermore, an average of three manual redeploy cycles are required to verify a single AI-suggested code fix in production ...

Many organizations describe AI as strategic, but they do not manage it strategically. When AI plans are disconnected from strategy, detached from organizational learning, and protected from serious assumptions testing, the problem is no longer technical immaturity; it is a failure of management discipline ... Executives too often tell organizations to "use AI" before they define what AI is supposed to change. The problem deepens in organizations where strategy isn't well articulated in the first place ...

Across the enterprise technology landscape, a quiet crisis is playing out. Organizations have run hundreds, sometimes thousands, of generative AI pilots. Leadership has celebrated the proof of concept (POCs) ... Industry experience points to a sobering reality: only 5-10% of AI POCs that progress to the pilot stage successfully reach scaled production. The remaining 90% fail because the enterprise environment around them was never ready to absorb them, not the AI models ...

Today's modern systems are not what they once were. Organizations now rely on distributed systems, event-driven workflows, hybrid and multi-cloud environments and continuous delivery pipelines. While each adds flexibility, it also introduces new, often invisible failures. Development speed is no longer the primary bottleneck of innovation. Reliability is ...

Seeing is believing, or in this case, seeing is understanding, according to New Relic's 2025 Observability Forecast for Retail and eCommerce report. Retailers who want to provide exceptional customer experiences while improving IT operations efficiency are leaning on observability ... Here are five key takeaways from the report ...