Cannon, > On Dec 17, 2016, at 7:22 PM, Cannon Smith <[email protected]> > wrote: > > I think there used to be a Debug Log Analyzer tool for v11. Does anyone know > if there is something similar for the new debug log format in v14+? Something > that would work with v16 log files?
Just Carr posted the link below recently. Very helpful and well done. Many thanks to Justin. Side note: I just noticed a problem with debug log analysis involving large objects. 4D apparently tries to stringify the entire object for every call where it is passed as a parameter. With debug logging on, any call with a large object parameter takes a long time even though 4D only writes a small amount of the JSON parameter to the log file. John DeSoi, Ph.D. > > On Dec 4, 2016, at 10:55 PM, Justin Carr <[email protected]> > wrote: > > > As long as you're using the "new" v14 log format, this should meet the > "looking at" part of the requirement: > > https://github.com/j-genie/4D-DebugLogReader > > Note that the log files are parsed into memory for performance reasons, so > there is a limit on how many you can process at a time. We tend to limit it > to 5 at a time. > ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
