Accordingly, the parameter specification for the 'dblogs' and 'applogs' example discussed above can be: In this case, the display names 'dblogs' and 'applogs' will alone be displayed as descriptors of this test.Įvery time this test is executed, the eG agent verifies the following: Your alertfile specification can also be of the following format: Here, Name represents the display name of the path being configured. In this case, the eG agent first enumerates all the log files in the specified path that match the given pattern, and then picks only the latest log file from the result set for monitoring. Here, '*' indicates leading/trailing characters (as the case may be). For example, to monitor the latest log files with names containing the strings 'dblogs' and 'applogs', the parameter specification can be, /tmp/db/*dblogs*,/tmp/app/*applogs*. Specific log file name patterns can also be specified. This ensures that eG Enterprise monitors the most recent log files in the specified directory. Multiple log file paths can be provided as a comma-separated list - eg., /user/john/critical_egurkha.log,/tmp/log/major.log.Īlso, instead of a specific log file path, the path to the directory containing log files can be provided - eg., /user/logs. port – The port at which the server listensĪlertfile - Specify the path to the log file to be monitored.Host - The host for which the test is to be configured.TEST PERIOD - How often should the test be executed.Outputs of the test : One set of results for every ALERTFILE and SEARCHPATTERN combination.
#A LOG FILE MONITOR UPDATE#
To enable this test, click on the check box corresponding to the test name in the disabled tests list of the agents – tests configuration page that appears when the Agents -> Tests -> Configure menu sequence is followed, and click the Update button therein.Īgent deploying the test : An internal agent This test monitors multiple log files for different error patterns.
0 kommentar(er)
