From SeedCode Documentation

GoZync3: ReadingTheLogs

These are the notes for GoZync 3. Docs for the latest version of GoZync--GoZync 4--can be found here. GoZync 4 is a free upgrade and is highly recommended (hint: it's faster).

Using the Zync logs for debugging and tuning

There are two logs in GoZync, formatted exactly the same way:

GoZyncMobile has the latest ZyncLog and the latest Package processed on that device.

GoZyncHosted has a Zync Log tab with the last Zync log for each syning device. (The latest package processed on the host can be found in the [[Inbox Processing | InBox.)

Logs look like this:

Aside from just reading what went down with a sync, here are a few tips to help you make sense of a log, and some tips on how to use them:

Split Times. The time codes to the left of the log indicate how long a step took. The first time is the "split" or the time since the last step, the total is the elapsed time so far.
Steps being timed. Obviously not every single thing that is happening in a sync is getting logged, but if you want to add more split times, it's pretty simple. In any script, at any point, add this SetVariable line:
SetVariable [$NoResult ; Value:gz_Timer_Split( "some message" )]
Finding Scripts. Let's say you see a log entry and want to find the script performing that step. Simply copy the text of the entry ("Connecting to Server" for example) and search the scripts (in both GZM and GZH) for that phrase. (Search scripts using the awesome developer assistant from Dracoventions.
Retrieved from http://archive.seedcode.com/pmwiki/pmwiki.php?n=GoZync3.ReadingTheLogs
Page last modified on August 05, 2013, at 04:21 AM