Tibco EMS Log Test

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.

Target of the test : A Tibco EMS Server

Agent deploying the test : An internal agent

Outputs of the test : One set of results for Tibco EMS server being monitored.

Configurable parameters for the test
Parameter Description

Test Period

How often should the test be executed.

Host

The IP address of the host for which this test is to be configured.

Port

Refers to the port at which the specified host listens to.

CommandPath

Prior to monitoring the Tibco EMS server, you will have to build a .bat or .sh file (depending upon the operating system on which Tibco EMS is functioning) bundled with the commands that the eG agent needs to execute on the Tibco EMS server for collecting the required metrics. The commands to be invoked by the .bat or .sh file are provided in How does eG Enterprise Monitor Tibco EMS?.

The .bat/.sh file so created can be saved to any location on the Tibco EMS host. Then, while configuring this test, make sure you provide the full path to this .bat or .sh file in the CommandPath text box so that, the agent can execute the file, invoke the commands bundled into it, and extract the desired metrics from the server.

Measurements made by the test
Measurement Description Measurement Unit Interpretation

Log file size

Indicates the current size of the log file.

KB

 

Max log file 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.

Log file usage

Indicates the percentage of allocated space that is currently used by the log file.

Percent

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.