On Thu, 2009-06-25 at 17:30 +0000, Kevin Thorley wrote: > On Thu, 25 Jun 2009 13:10:32 -0400, Martin Steinmann wrote: > > > Would that allow you to see what changed or only the fact that something > > changed? > > --martin > > > > Thats up to whoever writes the log statements for a given feature. Scott > had requested something like the following in the jira issue: > > "user 133 added forwarding to 388" > > The actual log entry would end up being along the lines of: > "2009-06-25 12:18:06,798":200:"Added forwarding to 388" > > It may help to add another field for type of message, such as > "Replication", "ConfigChange", "ServiceStateChange", etc. So we would > have log messages that look like this: > > > "2009-06-25 12:18:06,798":200:ConfigChange:"Added forwarding to 388" > "2009-06-25 12:18:06,798":200:Replication:"Replicated alarm-config.xml to > sipx.example.com" > "2009-06-25 12:18:06,798":200:ServiceStateChange:"Restarted sipXproxy"
+1 > Now, the real trick would be to add some sort of change tracking so we > could have a numeric id that would follow all steps of a change, from the > config change itself to the replication to the service restart. > Filtering the log on this id would show each step of the process to get a > config change to actual happen. I'm not ready to propose a way to do > this yet :) not needed now _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
