This means that when a line in the alert file matches a particular pattern, then x lines before the matched line and y lines after the matched line will be reported in the detail diagnosis output (in addition to the matched line).
This indicates that by default, the test will monitor only those lines in the dev_webdisp which embed the strings ERROR and WARN.
Therefore, the default SearchPattern is set as: ConnectionError:*ERROR*,warn:*WARN*. If you want all the messages in a log file to be monitored, then your specification would be: :*.īy default, this test monitors error and warning events logged in the dev_webdisp file. Multiple search patterns can be specified as a comma-separated list. A leading '*' signifies any number of leading characters, while a trailing '*' signifies any number of trailing characters. The pattern should be in the following format: :, where is the pattern name that will be displayed in the monitor interface and is an expression of the form - *expr* or expr or *expr or expr*, etc. If an older log file has been overwritten, then, the eG agent monitors this log file completely, and then proceeds to monitor the newer log files (if any).Įnter the specific patterns of alerts to be monitored. If a few lines have been added to a log file that was monitored previously, then the eG agent monitors the additions to that log file, and then proceeds to monitor newer log files (if any). Whether any new log files (that match the AlertFile specification) have been newly added since the last measurement period.Whether any changes have occurred in the size and/or timestamp of the log files that were monitoring during the last measurement period.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.Įvery time this test is executed, the eG agent verifies the following: Here, '*' indicates leading/trailing characters (as the case may be). For example, to monitor the latest log files with names containing the string dev_webdisp, the parameter specification can be, /opt/egurkha/manager/*dev_webdisp*. Specific log file name patterns can also be specified. This ensures that eG Enterprise monitors the most recent log files in the specified directory. Since the dev_webdisp is by default found in the SAP Web Dispatcher directory, the same is displayed here by default.Īlso, instead of a specific log file path, the path to the directory containing the dev_webdisp files can be provided - eg., /opt/egurkha/manager/logs.
#Sap installation log file location full
Specify the full path to the log file to be monitored. The port number at which the specified host listens. Specify the host for which the test is to be configured.
Configurable parameters for the test Parameter Outputs of the test : One set of results for each error type detected in the target SAP Web Dispatcher being monitored. Target of the test : A SAP Web DispatcherĪgent deploying the test : An internal agent By periodically parsing this dev_webdisp_log and retrieving the details of error/warning events logged therein, you can understand which activities failed and why. The SAP Web Dispatcher, automatically creates a dev_webdisp_log in the SAP WEB DISPATCHER directory to which errors/warnings captured during installation, configuration and control (starting/stopping) of the SAP Web Dispatcher are recorded.