By setting this parameter to TRUE, you can instruct the test to ignore a line and move to the next as soon as a match for one of the configured patterns is found in that line. However, you can add more file formats to the default list in the following format: ' *.gz,*.tar,*.zip, *cab, *7z, *rar'.īy default, the UNIQUEMATCH parameter is set to FALSE, indicating that, by default, the test checks every line in the log file for the existence of each of the configured SEARCHPATTERN. By default, this parameter is set to ' *.gz,*.tar,*.zip' indicating that the files of the mentioned formats will be excluded from monitoring by the test. Provide a comma-separated list of file formats to be excluded from monitoring in the ExcludeFiles text box. By default, this parameter is set to 'none'. ![]() Provide a comma-separated list of patterns to be excluded from monitoring in the EXCLUDEPATTERN text box. If you give 0:0,1:1,2:1 as the value for LINES and if the corresponding value in the SEARCHPATTERN field is like ORA:ORA-*,offline:*offline*,online:*online then:ġ:1 will be applied to offline:*offline* patternĢ:1 will be applied to online:*online pattern If you give 1:1 as the value for LINES, then this value will be applied to all the patterns specified in the SEARCHPATTERN field. Multiple entries can be provided as a comma-separated list. This means that when a line in the log 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). The searchpattern specification in this case will hence be as you want all the messages in a log file to be monitored, then your specification would be: :* On the other hand, if the alertfile specification consists only of a comma-separated list of log file paths, then the descriptors will be of the format: LogFilePath:PatternName.Īlso, if a comma-separated list of alert files is provided in the alertfile text box in the format and you want to monitor one/more specific patterns of logs in each alert file, then your specification would be of the instance, say, your alertfile specification is as follows: Now, assume that you want to monitor the following entries in the specified alert files: Alert file If the alertfile specification is of the format then the descriptor for this test in the eG monitor interface will be of the format: Name:PatternName. For example: ORA:ORA-*,offline:*offline*,online:*online Multiple search patterns can be specified as a comma-separated list. ![]() ![]() That is, the is matched if either e1 is true or e2 is true. Similarly, if your pattern specification reads: offline:*offline, then it means that the pattern name is offline and that the test will monitor those lines in the log file which end with the term offline.Ī single pattern may also be of the form e1+e2, where + signifies an OR condition. "ORA-*" indicates that the test will monitor only those lines in the log file which start with the term "ORA-". This indicates that "ORA" is the pattern name to be displayed in the monitor interface. ![]() A leading '*' signifies any number of leading characters, while a trailing '*' signifies any number of trailing characters.įor example, say you specify ORA:ORA-* in the SEARCHPATTERN text box. To enable the test, go to the enable / disable tests page using the menu sequence : Agents -> Tests -> Enable/Disable, pick the desired Component type, set Performance as the Test type, choose the test from the DISABLED TESTS list, and click on the :, 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. This test monitors multiple log files for different error patterns.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |