Debug log analyzer v14

[Two Way Communications via 4D_Tech]

Has anybody used the newest Debug log analyzer?


It seems to me that there are some bugs in it.

e.g., when I get the list of ’top’ calls, it lists a specific method as being 
called 22 times in a selected process.

If I than look at all the operations for that process, which is another tab, 
and there, the method occurs in only 3 occasions…


Regards,

Rudy Mortier
Two Way Communications bvba 



**
4D Internet Users Group (4D iNUG)
Archive:  http://lists.4d.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
**

Re: Debug Log Analyzer

[Cannon Smith]

Hi Justin,

Thanks for these tools. I ended up getting the data I needed on Saturday before 
I learned about them, but I’ll definitely keep the around.

Thanks.

--
Cannon Smith
Synergy Farm Solutions Inc.
Hill Spring, AB Canada
403-626-3236
<can...@synergyfarmsolutions.com>



> On Dec 18, 2016, at 5:44 PM, Justin Carr <justinc...@geniesolutions.com.au> 
> wrote:
> 
> Aside from our debug parser, there is a new version of the debug log analyzer 
> which works with the v14+ log file format: http://kb.4d.com/assetid=77198

**
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:4d_tech-unsubscr...@lists.4d.com
**

Re: Debug Log Analyzer

[Justin Carr]

On 18 Dec 2016, at 11:22 am, Cannon Smith <can...@synergyfarmsolutions.com> 
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?

Hi Cannon

Aside from our debug parser, there is a new version of the debug log analyzer 
which works with the v14+ log file format: http://kb.4d.com/assetid=77198

Which to use depends on your requirements. The analyzer tool provides more 
aggregated data so you can see things like which commands are used the most, or 
take the longest, etc.

Our debug parser provides the commands with parameters as they were called, in 
order, and separated by process and log session. It is more useful if you're 
trying to track where an application is crashing or why it isn't behaving as 
you would expect.

Regards
Justin
**
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:4d_tech-unsubscr...@lists.4d.com
**

Re: Debug Log Analyzer

[Cannon Smith]

Thank you, John! I missed that completely.

--
Cannon Smith
Synergy Farm Solutions Inc.
Hill Spring, AB Canada
403-626-3236




> On Dec 17, 2016, at 7:55 PM, John DeSoi  wrote:
> 
> Just Carr posted the link below recently. Very helpful and well done. Many 
> thanks to Justin.

**
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:4d_tech-unsubscr...@lists.4d.com
**

Re: Debug Log Analyzer

[John DeSoi]

Cannon,

> On Dec 17, 2016, at 7:22 PM, Cannon Smith <can...@synergyfarmsolutions.com> 
> 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 <justinc...@geniesolutions.com.au> 
> 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:4d_tech-unsubscr...@lists.4d.com
**

Debug Log Analyzer

[Cannon Smith]

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?

Thanks.

--
Cannon Smith
Synergy Farm Solutions Inc.
Hill Spring, AB Canada
403-626-3236
<can...@synergyfarmsolutions.com>



**
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:4d_tech-unsubscr...@lists.4d.com
**