Now that Martin P. is getting the extraction of logs working, I think that we should clean up our strategy with regard to extracting logs that do not have the standard sipXecs "syslog" format. Up to now, we did not extract logs more than 1 day old (or we didn't do it correctly, so nobody ever asked for it), and so we could incorporate the entirety of any current non-syslog log file and be sure of capturing the time interval of interest.
Now that we are going to extract logs from past days, that crude strategy is pretty much useless. So I am proposing that we properly extract subsets of the non-syslog log files. This probably isn't very difficult, since our extraction programs are written in a scripting language (Ruby? Python?), but I want to discuss it here first, in case there are unexpected complications. One complication is that many programs (e.g., httpd) want to timestamp their log lines using local time rather than UTC. Could this be fixed by setting the timezone the program operates under to UTC? (Would this affect other actions of the programs?) And sometimes the log lines are timestamped using English, so I suppose there might be language-configuration problems. (There are other technical points I want to discuss about the log extraction process, but they should only be of interest to implementors thereof. I also have undone work with regard to Martin's improvements, which is finally getting to the top of my stack.) Comments? Dale _______________________________________________ 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/
