Documentation/Nightly/SlicerApplication/ErrorLog - Revision history

Lasso: /* Analyze error log */

2018-09-25T16:22:33Z

Analyze error log

Lasso: /* To capture the entire error log for a report */

2018-09-25T16:21:45Z

To capture the entire error log for a report

Pinter at 20:20, 17 April 2018

2018-04-17T20:20:05Z

Pieper at 13:24, 20 February 2015

2015-02-20T13:24:37Z

Pieper at 13:23, 20 February 2015

2015-02-20T13:23:18Z

UpdateBot: Prepend documentation/versioncheck template. See http://na-mic.org/Mantis/view.php?id=2887

2013-06-14T07:53:34Z

Prepend documentation/versioncheck template. See http://na-mic.org/Mantis/view.php?id=2887

JChris.FillionR: 4.1 -> Nightly

2012-08-22T16:59:39Z

4.1 -> Nightly

New page

[[Image:ErrorLogDialog.png|thumb|center|600px|Error Log dialog]]
The error log dialog is accessible from ''View -> Error Log'' or via the ''Ctrl+0'' shortcut.

All the outputs (errors, warnings, messages, information) generated by the application and modules are gathered in this dialog. This readout is useful for reporting bugs or usability problems back to the Slicer Development Team.

The dialog is split in 2 parts, the top section is a digest listing of outputs that are merged by type and time. If multiple errors are output within a short period (<1ms) of time from a given component, they will show up as 1 item in the digest list. The bottom section of the dialog prints all the details of the digest list. Selecting one or multiple items in the digest list, results in the printing of all merged lines in the detailed bottom list.

When reporting a bug on the mailing list or in the bug tracker, it is valuable information to include a dump of the errors that appear in the Error Log dialog.

← Older revision		Revision as of 16:22, 25 September 2018
Line 37:		Line 37:
	* Log file timestamp format: <code>dd.mm.yyyy HH:mm:ss</code>		* Log file timestamp format: <code>dd.mm.yyyy HH:mm:ss</code>

−	[[Image:~~ApacheChainsawLogAanalysis~~.png\|thumb\|center\|600px\|Viewing and filtering logs using Apache Chainsaw]]	+	[[Image:ApacheChainsawLogAnalysis.png\|thumb\|center\|600px\|Viewing and filtering logs using Apache Chainsaw]]

← Older revision		Revision as of 16:21, 25 September 2018
Line 24:		Line 24:
	* Paste from clipboard into your email or issue report		* Paste from clipboard into your email or issue report
	-->		-->
		+
		+	==Analyze error log==
		+
		+	Error log viewer applications can be used for convenient searching and filtering of error logs.
		+
		+	For example, [logging.apache.org/chainsaw/ Apache Chainsaw] log viewer can load and parse Slicer logs using this configuration:
		+
		+	* Select ''Process a log file''
		+	* Log file URL: choose use ''Open File...'' button to select file
		+	* Log file format type: ''PatternLayout format''
		+	* Log file format: <code>[LEVEL][LOGGER] TIMESTAMP [CLASS] (FILE) - MESSAGE</code>
		+	* Log file timestamp format: <code>dd.mm.yyyy HH:mm:ss</code>
		+
		+	[[Image:ApacheChainsawLogAanalysis.png\|thumb\|center\|600px\|Viewing and filtering logs using Apache Chainsaw]]

@@ Line 10: / Line 10: @@
 ==To capture the entire error log for a report==
 * Click in the ErrorLog dialog '''top''' section
 * Type Control-A to '''select all''' (Command-A on Mac)
@@ Line 16: / Line 23: @@
 * Type Control-C to '''copy''' (Command-C on Mac)
 * Paste from clipboard into your email or issue report

@@ Line 9: / Line 9: @@
 When reporting a bug on the mailing list or in the bug tracker, it is valuable information to include a dump of the errors that appear in the Error Log dialog.
-* To capture the entire error log for a report:
+==To capture the entire error log for a report==
-** Click in the ErrorLog dialog '''top''' section
+* Click in the ErrorLog dialog '''top''' section
-** Type Control-A to '''select all''' (Command-A on Mac)
+* Type Control-A to '''select all''' (Command-A on Mac)
-** Click in the ErrorLog dialog '''bottom''' section
+* Click in the ErrorLog dialog '''bottom''' section
-** Type Control-A to '''select all''' (Command-A on Mac)
+* Type Control-A to '''select all''' (Command-A on Mac)
-** Type Control-C to '''copy''' (Command-C on Mac)
+* Type Control-C to '''copy''' (Command-C on Mac)
-** Paste from clipboard into your email or issue report
+* Paste from clipboard into your email or issue report

← Older revision		Revision as of 13:23, 20 February 2015
Line 8:		Line 8:

	When reporting a bug on the mailing list or in the bug tracker, it is valuable information to include a dump of the errors that appear in the Error Log dialog.		When reporting a bug on the mailing list or in the bug tracker, it is valuable information to include a dump of the errors that appear in the Error Log dialog.
		+
		+	* To capture the entire error log for a report:
		+	** Click in the ErrorLog dialog '''top''' section
		+	** Type Control-A to '''select all''' (Command-A on Mac)
		+	** Click in the ErrorLog dialog '''bottom''' section
		+	** Type Control-A to '''select all''' (Command-A on Mac)
		+	** Type Control-C to '''copy''' (Command-C on Mac)
		+	** Paste from clipboard into your email or issue report

← Older revision		Revision as of 07:53, 14 June 2013
Line 1:		Line 1:
		+	<noinclude>{{documentation/versioncheck}}</noinclude>
	[[Image:ErrorLogDialog.png\|thumb\|center\|600px\|Error Log dialog]]		[[Image:ErrorLogDialog.png\|thumb\|center\|600px\|Error Log dialog]]
	The error log dialog is accessible from ''View -> Error Log'' or via the ''Ctrl+0'' shortcut.		The error log dialog is accessible from ''View -> Error Log'' or via the ''Ctrl+0'' shortcut.