atom feed9 messages in org.codehaus.esper.dev[esper-dev] [jira] Updated: (ESPER-15...
FromSent OnAttachments
ming Fang (JIRA)Sep 6, 2007 11:39 am 
ming Fang (JIRA)Sep 6, 2007 11:41 am 
Thomas Bernhardt (JIRA)Sep 6, 2007 12:57 pm 
Thomas Bernhardt (JIRA)Sep 6, 2007 12:57 pm 
Thomas Bernhardt (JIRA)Jan 27, 2008 11:36 am 
Thomas Bernhardt (JIRA)Oct 20, 2008 11:44 am 
Thomas Bernhardt (JIRA)Jan 2, 2009 9:20 am 
Thomas Bernhardt (JIRA)Sep 17, 2009 4:13 am 
Thomas Bernhardt (JIRA)Jul 30, 2010 12:26 pm 
Subject:[esper-dev] [jira] Updated: (ESPER-156) Fully auditing facility
From:Thomas Bernhardt (JIRA) (ji@codehaus.org)
Date:Oct 20, 2008 11:44:20 am
List:org.codehaus.esper.dev

[
http://jira.codehaus.org/browse/ESPER-156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Thomas Bernhardt updated ESPER-156:

Fix Version/s: (was: 2.3) 3.0

Fully auditing facility

-----------------------

Key: ESPER-156 URL: http://jira.codehaus.org/browse/ESPER-156 Project: Esper Issue Type: Wish Affects Versions: 2.3 Reporter: Ming Fang Fix For: 3.0

It would be very useful for Esper to provide full auditing capability. Something like a AuditListener interface that would get callbacks from Esper on
every 1-sendEvent 2-every stream created or destroyed 3-every firing of matches 4-every window created or destroyed 5-every statement created or destroyed 6-etc I can see many uses for this 1-tools to visualize what's happening 2-potentially a journalling mechanism to replay on another instance for
recovery, like a db journal log 3-as hook for performances instrumentation