Web Portal Sections:Logs - Revision history

Cbilodeau: rephrase page

2011-03-01T20:23:18Z

rephrase page

← Older revision		Revision as of 15:23, 1 March 2011
Line 1:		Line 1:
	The Logs section of the [[Web Portal]] enables you to access all of the logs stored in the file system. By default the ~~filename pop~~-~~up menu~~ is filled with the paths of common Toolpack log files, where the name of each log is the actual path to that file on the system. ~~(By the way, if you are not currently displaying the notes section, you may want to do so now so that you can view additional details.)~~		The Logs section of the [[Web Portal]] enables you to access all of the logs stored in the file system. By default the drop-down box is filled with the paths of common Toolpack log files, where the name of each log is the actual path to that file on the system.

	~~There are system logs and Toolpack logs.~~ The ~~system log is called production.log. It records each and every web server access, as well as detailed information if a view crashes.~~		The Toolpack logs correspond to various application instances that run on the device:
			'''gateway_.log'''; it features information relative to the gateway (see [[Toolpack_Application:gateway\|gateway application]]).
			'''toolpack_engine_.log'''; it features information relative to the 'dynamic' resource allocation of the system (see [[Toolpack_Application:toolpack_engine\|toolpack_engine]]).
	~~The other logs are the~~ Toolpack logs~~, which~~ correspond to various application instances that run on the device~~. They are~~:		'''toolpack_sys_mgr_.log'''; it features information relative to the 'static' resource allocation of the system (see [[Toolpack_Application:toolpack_sys_manager\|sys_manager]]).
	'''gateway_.log'''; it features information relative to the gateway (~~high level call handling~~).		'''tboam_app_.log'''; it features information relative to the system management (see [[Toolpack_Application:tboamapp\|tboamapp]]).
	'''toolpack_engine_.log'''; it features information relative to the ~~engine~~ (~~low level call handling~~).
	'''toolpack_sys_mgr_.log'''; it features information relative to the ~~sys manager~~ (~~system configuration~~).
	'''tboam_app_.log'''; it features information relative to the ~~oamapp (~~system management).
	'''web_status_client_.log'''; it features the web server oam wrapper log (not useful).		'''web_status_client_.log'''; it features the web server oam wrapper log (not useful).


	The options for querying logs are as follows:		The options for querying logs are as follows:
	*'''Tail + number of lines'''; this will show the number of lines working back from the end of the log		*'''Tail + number of lines'''; this will show the number of lines working back from the end of the log
	*'''Head + number of lines'''; this will show the number of lines working forward from the start of the log		*'''Head + number of lines'''; this will show the number of lines working forward from the start of the log
Line 23:		Line 20:


	~~With the exception of the production log file, which is not rotated,~~ Toolpack logs are rotated daily or when they get to 10MB. They are then zipped (using gzip) to save space. Logs are deleted when the total gzipped logs file size for one application reaches 100MB (default). This 100MB limit can be modified per application through the Web Portal configuration.		Toolpack logs are rotated daily or when they get to 10MB. They are then zipped (using gzip) to save space. Logs are deleted when the total gzipped logs file size for one application reaches 100MB (default). This 100MB limit can be modified per application through the Web Portal configuration.

Ktrueman: fixed link

2010-05-27T15:16:12Z

fixed link

← Older revision		Revision as of 10:16, 27 May 2010
Line 1:		Line 1:
	The Logs ~~[[Web Portal Sections\|~~section]] of the [[Web Portal]] enables you to access all of the logs stored in the file system. By default the filename pop-up menu is filled with the paths of common Toolpack log files, where the name of each log is the actual path to that file on the system. (By the way, if you are not currently displaying the notes section, you may want to do so now so that you can view additional details.)		The Logs section of the [[Web Portal]] enables you to access all of the logs stored in the file system. By default the filename pop-up menu is filled with the paths of common Toolpack log files, where the name of each log is the actual path to that file on the system. (By the way, if you are not currently displaying the notes section, you may want to do so now so that you can view additional details.)

	There are system logs and Toolpack logs. The system log is called production.log. It records each and every web server access, as well as detailed information if a view crashes.		There are system logs and Toolpack logs. The system log is called production.log. It records each and every web server access, as well as detailed information if a view crashes.

Ktrueman: initial content taken from training module 210

2010-05-27T14:36:23Z

initial content taken from training module 210

New page

The Logs [[Web Portal Sections|section]] of the [[Web Portal]] enables you to access all of the logs stored in the file system. By default the filename pop-up menu is filled with the paths of common Toolpack log files, where the name of each log is the actual path to that file on the system. (By the way, if you are not currently displaying the notes section, you may want to do so now so that you can view additional details.)

There are system logs and Toolpack logs. The system log is called production.log. It records each and every web server access, as well as detailed information if a view crashes.

The other logs are the Toolpack logs, which correspond to various application instances that run on the device. They are:
*'''gateway_*.log'''; it features information relative to the gateway (high level call handling).
*'''toolpack_engine_*.log'''; it features information relative to the engine (low level call handling).
*'''toolpack_sys_mgr_*.log'''; it features information relative to the sys manager (system configuration).
*'''tboam_app_*.log'''; it features information relative to the oamapp (system management).
*'''web_status_client_*.log'''; it features the web server oam wrapper log (not useful).

The options for querying logs are as follows:
*'''Tail + number of lines'''; this will show the number of lines working back from the end of the log
*'''Head + number of lines'''; this will show the number of lines working forward from the start of the log
*'''Line + start line + number of lines'''; this will show the number of lines starting from the start line that you selected

After selecting an option, you can choose one of two courses of action:
*'''View'''; this will display the output in the web view
*'''Download'''; this will start a download dialog for the requested log section

With the exception of the production log file, which is not rotated, Toolpack logs are rotated daily or when they get to 10MB. They are then zipped (using gzip) to save space. Logs are deleted when the total gzipped logs file size for one application reaches 100MB (default). This 100MB limit can be modified per application through the Web Portal configuration.