Exception Log Test
This test reports general statistics pertaining to the log files in a host.
Target of the test : Any host
Agent deploying the test : An internal agent
Outputs of the test : One set of results for the server being monitored.
Parameter | Description |
---|---|
Test Period |
How often should the test be executed. |
Host |
Host name/IP address of the server for which the test is to be configured |
PortNo |
The port on which the specified server listens for HTTP requests |
LogFile |
The name of the log file to be monitored. |
LogDir |
The full path to the specified log file. |
EmptyFile |
Enter either true or false. The entry true instructs the eG Enterprise to monitor even empty log files. The entry false instructs the eG Enterprise to ignore empty log files during monitoring. By default, this text box will hold the value false. |
HighPattern |
In order to track critical exceptions logged in the log file, you need to specify the pattern of such exceptions, here. For eg., if critical exception logs contain the string "Error", then your pattern specification could be *Error*. A leading '*' signifies any number of leading characters, while a trailing '*' signifies any number of trailing characters. |
LowPattern |
To monitor minor exceptions logged in the log file, the pattern of the minor exceptions has to be specified in this text box. For eg., if minor exception logs contain the string "Low", then the pattern specification could be *Low*. A leading '*' signifies any number of leading characters, while a trailing '*' signifies any number of trailing characters. |
MediumPattern |
For monitoring the medium exceptions in the log file, the pattern of these exceptions needs to be defined in this text box. For eg., if medium exception logs contain the string "Warning", then the pattern specification could be *Warning*. A leading '*' signifies any number of leading characters, while a trailing '*' signifies any number of trailing characters. |
Measurement | Description | Measurement Unit | Interpretation |
---|---|---|---|
Total exceptions |
Indicates the total number of exceptions logged in the log file |
Number |
A high value of this measure indicates the need to analyze the exceptions, ascertain their severity, and take corrective action if required. |
High exceptions |
Indicates the number of critical exceptions that have been logged in the log file |
Number |
System performance will suffer much on the occurrence of critical exceptions. Such exceptions will have to be fixed with immediate effect. |
Medium exceptions |
Indicates the number of not-very-critical exceptions logged in the log file |
Number |
Medium exceptions might not have an immediate impact on the system performance, but, in the long run, they could grow to be fatal. Such exceptions need not be looked into immediately, but will have to be fixed soon enough. |
Low exceptions |
Indicates the number of very minor exceptions in the log file |
Number |
Low exceptions are very negligible in nature and can be ignored. |
Note:
If a log file to be monitored is not found or is empty, then the errcount will be 0.