Building EchoOps: How Persistent Memory Helps Incident-Response Agents Avoid Repeating Failed Actions

Mohan kumar Duppada — Tue, 29 Sep 2026 18:23:55 +0000

Production incidents are difficult not only because systems fail, but because the same failures can happen again.

An incident-response system may know how to troubleshoot a 503 error, but what happens if it does not remember that a particular troubleshooting step already failed during a previous incident?

That was the problem behind EchoOps.

We built EchoOps as an incident-response decision-support prototype that uses persistent experience memory to make better decisions during similar future incidents.

The main idea is simple:

Remember what happened. Remember what failed. Remember what worked. Use that experience next time.

What Is EchoOps?

EchoOps is a focused incident-response prototype for software and SRE scenarios.

The system simulates an incident, investigates it, recalls relevant previous experiences, recommends an action, observes the result, and then stores the experience for future incidents.

The learning loop looks like this:


text
Incident
   ↓
Investigate
   ↓
Recall Previous Experience
   ↓
Make Recommendation
   ↓
Take / Simulate Action
   ↓
Observe Outcome
   ↓
Retain Experience
   ↓
Future Similar Incident

DEV Community: Mohan kumar Duppada

Building EchoOps: How Persistent Memory Helps Incident-Response Agents Avoid Repeating Failed Actions

What Is EchoOps?