|
Default Parameters for BobiLSLogTest
This test periodically monitors the logs of Lumira server and reports metrics such as errors, important messages, fatal messages, etc. so that critical problem events can be quickly captured and resolved.
This page depicts the default parameters that need to be configured for the BobiLSLogTest.
LOG DIRECTORY is the directory to which logs from various nodes installed on a host are written. Typically, these logs are written to ‘*.glf’ files in the ‘logging’ directory of the BOBI installation. If SAP BOBI is installed in the C drive of a Windows host, the logging directory will be available in the following location by default: C:\Program Files(x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\
Log file names are generally of the following format : <server abbreviation>_<node name>.<server type>*.glf’ For e.g., cms_SAPBOBI.CentralManagementServer_trace.001284 is one of the log trace files from the Central Management Server running in the node called SAPBOBI. Server abbreviation in this case is cms. The default value for SERVER ABBREVIATIONS parameter has hence been set as a comma separated list of server descriptions and their abbreviations as follows : <server description>:<server abbreviation>. For trace files of the Central Management Server, Adaptive Processing Server and Adaptive Job Server, SERVER ABBREVIATIONS parameter has been by default set as: Central Management Servers:CMS,Adaptive Processing Servers:aps,Adaptive Job Servers:jobserver, Lumira server:LS.
Enter the specific patterns of messages to be monitored in the SEARCH PATTERN textbox. The pattern should be in the following format: <PatternName>:<Pattern>, where <PatternName> is the pattern name that will be displayed in the monitor interface and <Pattern> is an expression of the form - *expr* or expr or *expr or expr*, etc. A leading ‘*rsquo; signifies any number of leading characters, while a trailing ‘*’ signifies any number of trailing characters.
For example, say you specify ORA:ORA-* in the SEARCH PATTERN text box. This indicates that “ORA” is the pattern name to be displayed in the monitor interface. “ORA-*” indicates that the test will monitor only those lines in the log file which start with the term “ORA-”. 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.
A single pattern may also be of the form e1+e2, where + signifies an OR condition. That is, the <PatternName> is matched if either e1 is true or e2 is true.
Multiple search patterns can be specified as a comma-separated list. For example: ORA:ORA-*,offline:*offline*,online:*online.
Each of these patterns will be searched for in every log file that is present in the configured Log Directory.
Specify two numbers in the format x:y in the LINES text box. 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 default value here is 0:0. Multiple entries can be provided as a comma-separated list. 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. If you give 0:0,1:1,2:1 as the value for Lines and if the corresponding value in the SearchPattern filed is like ORA:ORA- *,offline:*offline*,online:*online then:
0:0 will be applied to ORA:ORA-* pattern 1:1 will be applied to offline:*offline* pattern 2:1 will be applied to online:*online pattern
By 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 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. For example, assume that Pattern1:*fatal*,Pattern2:*error*is the SearchPattern that has been configured. If UniqueMatch is set to False, then the test will read every line in the log file completely to check for the existence of messages embedding the strings ‘fatal’ and ‘error’. If both the patterns are detected in the same line, then the number of matches will be incremented by 2. On the other hand, if UniqueMatch is set to True, then the test will read a line only until a match for one of the configured patterns is found and not both. This means that even if the strings ‘fatal’ and ‘error’ follow one another in the same line, the test will consider only the first match and not the next. The match count in this case will therefore be incremented by only 1.
ROTATING FILE flag governs the display of descriptors for this test in the eG monitoring console.
If ROTATING FILE flag is set to True, the descriptors of this test will be displayed in the following format: <Full_Path_to_LogDirectory>:<ServerAbbreviation>. For instance, if the log directory parameter is set to c:\SAPBOBI\logs and RotatingFile is set to True, then, your descriptor will be of the following format: c:\SAPBOBI\logs:<ServerAbbreviation>. On the other hand, if the RotatingFile flag had been set to False, then the descriptors will be of the following format: <LogDirectory>:<ServerAbbreviation> - i.e., logs:<ServerAbbreviation> in the case of the example above.
If UTF-8 encoding is to be used for reading the log files in the configured log directory, then, set the USEUTF8 flag to True. By default, this flag is set to False.
If UTF-16 encoding is to be used for reading the log files in the configured log directory, then, set the USEUTF16 flag to True. By default, this flag is set to False.
By default, the ENCODEFORMAT is set to none, indicating that no encoding format applies by default. However, if the test has to use a specific encoding format for reading from the log files in the log directory, then you will have to provide a valid encoding format here - eg., UTF-8, UTF-16, etc.
PROVIDER parameter appears only if the Mode is set to JMX. This test uses a JMX Provider to access the MBean attributes of the target Java application and collect metrics. Specify the package name of this JMX Provider in the PROVIDER textbox. By default, this parameter is set to default indicating that this test automatically discovers the JMX provider and report metrics.
The DD FREQUENCY refers to the frequency with which detailed diagnosis measures are to be generated for this test. The default is 1:1. This indicates that, by default, detailed measures will be generated every time this test runs, and also every time the test detects a problem. You can modify this frequency, if you so desire. Also, if you intend to disable the detailed diagnosis capability for this test, you can do so by specifying none against DD FREQUENCY.
When changing default configurations of tests, the values with “$” indicate variables that will be replaced by the eG system according to the specific server being managed - for instance, $hostName is the host/nickname of the target host, $port is the port number of the server being monitored. E.g., for a server xyz:80, $hostName will be changed automatically by the eG manager to “xyz*” and $port will be changed to “80” when configuring a test.
|