It's funny, the reactions I get. A lot of startup programmers who have never worked on large systems don't understand why it's so valuable. But those who have done big enterprise use phrases like "holy grail".
But this is a HARD problem. Man, abstracting change in an actionable, readable, efficient way has been difficult. Not to mention the security issues and other headaches.
I'll bet, it's a truly monumental task to take on (so kudos for giving it a try), stuff I work on these days doesn't need that level of monitoring (We have 4 servers and a bunch of desktops laptops, it's pretty much vanilla small business stuff) but I know a few people who would love that kind of stuff.
It would do in software what a really good reliability engineer with years of knowledge can do "Foo has broken" "Nah foo is fine, someone changed Bar again without reading the wiki" stuff.