eG Help

The EMS server can be configured to write a variety of information to a log file. Server activities can be efficiently tracked using the information logged in the log files. Several parameters and commands control the location, logged information, and general configuration of the log files. One such parameter is the logfile_max_size configuration parameter that governs the maximum size upto which a log file can grow. To make sure that the log file does not grow boundlessly, this test periodically monitors the size of the log file and promptly alerts administrators if the log file is about to exceed the size limit set.

Measurement	Description	Measurement Unit	Interpretation
Log_file_size	Indicates the current size of the log file.	KB
Max_Logfile_size	Indicates the maximum allocated size of the log file.	KB	This measure typically returns the value set for the logfile_max_size configuration parameter.
LogFile_usepercentage	Indicates the percentage of allocated space that is currently used by the log file.	%	If the value of this measure is 100%, it indicates that the logfile_max_size threshold has been violated - i.e., the log file has reached its maximum size. In this case, the contents of the log file are copied to a file with the same name as the current log file, except that a sequence number is appended to the name of the backup file. The server queries the directory and determines the first available sequence number. For example, if the current log file is named tibems.log, the first copy is named tibems.log.1, the second is named tibems.log.2, and so on. To further regulare the space usage of the log files, you can also dynamically force the log file to be backed up and truncated using the rotatelog command in tibemsadmin.