Here's a link to EPL, a new programming language designed specifically for event processing and analysis:
<http://www.ispheres.com/>
There are many interesting overlaps with software project telemetry, the Telemetry Description Language, and alerts. I like our approach much better for our particular situation (and not just because ours was not Not Invented Here :-). For example, telemetry builds elegantly off the raw sensor data abstractions (i.e. Active Time, etc.). Unlike EPL, we don't need to support 30,000 events per second, nor provide real-time, time-critical notification (i.e. "The nuclear reactor core is about to blow!"). The combination means that our domain-specific design can be simpler, cheaper, lighter weight, and easier to understand and modify.
But it's cool to check them out because their approach, looked at from a high level, addresses so many of the same things we have been working on for quite a while. Cedric will be able to do a very interesting compare/contrast of EPL with TDL in his thesis proposal. In a way, it's a nice validation of software project telemetry.
In the much longer term, one could imagine an integration of EPL with Hackystat. I could see an EPL layer underneath Hackystat, in particular if they eventually support plugins for certain kind of data streams.
Cheers, Philip
