DebugLogAnalyzer

based on original work by Josh Fletcher

View the Project on GitHub miyako/DebugLogAnalyzer

version platform license downloads

DebugLogAnalyzer

based on original work by Josh Fletcher (2009)

dependencies.json

{
	"dependencies": {
		"DebugLogAnalyzer": {
			"github": "miyako/DebugLogAnalyzer",
			"version": "latest"
		}
	}
}

Modifications

page 1

analysis starts as soon as a set of debug log files or a folder is selected or dropped on the listbox

pages 2 to 4

Features

only the classic “human readable” debug log file can be analysed.

there are evidently 2 versions of this format:

cmd

1 p=1 puid=1 	(1) cmd: SET TIMER.
1	2025-04-01T18:27:13.284 p=1 puid=1	(1)  cmd: SET TIMER
2	2025-04-01T18:27:13.284 p=1 puid=1	(1)  end_cmd: SET TIMER. < ms

meth, mbr

1571 p=6 puid=8 meth: DBL_P_Import
1571 p=6 puid=8 end_meth: DBL_P_Import
19	2025-04-01T18:27:13.285 p=6 puid=8	(2)  meth: DBL_P_Import
50	2025-04-01T18:27:13.286 p=6 puid=8	(2)  end_meth: DBL_P_Import. < ms

form, obj

31 p=6 puid=8 form: IAS_CustomAlert; event: OnLoad
33 p=6 puid=8 end_form
11	2025-04-01T18:27:13.281 p=6 puid=10	(0)  form: IAS_CustomAlert during OnLoad
64	2025-04-01T18:27:13.286 p=6 puid=10	(0)  end_form: IAS_CustomAlert during OnLoad. 2 ms

Plugins

information about plugins are reported in 4 categories in a tabular debug log 2
the uniform format is `{number};{code}’.

the command number is their position in manifest.json. the number is the position in PLUGIN LIST. this is specific to the execution context. because plugins are not loaded in alphabetical order, it is not possible to trace a plugin number its list of command names. for that reason, information about commands and events are ignored in the TSV format.