Regex Logs Test

eG agent compares each line (row) in the log file with the format file pattern (containing regular expression) for its exact match. As a result, if the specific line in the log file is matched with the format pattern, then those lines in the log file are considered to be matched lines. Each line in the log file has unique keys based on the Duplicate Detection Key Attributes parameter. If the unique keys are identical with next matched line, then that next matched log lines are considered to be duplicate lines. If the specific line in the log file is not matched with the format pattern, then those lines are considered to be discarded lines. This test helps the administrator to monitor how long the target Regex Log Monitor takes to identify the matched, duplicate and discarded lines by comparing the log file with the format pattern and determine the cause if the Regex matching process gets delayed.

Target of the test : Regex Log

Agent deploying the test : An internal agent

Outputs of the test : One set of results for each Log file: Log Summary details in the target Regex Log.

Configurable parameters for the test
Parameter	Description
Test period/De-duplication Frequency	How often should the test be executed. This parameter also serves as deduplication test frequency where the duplicate lines are watched within this period.
Host	The IP address of the target Regex Log that is being monitored.
Port	The port number through which the Regex Log Monitor communicates. The default port is 8056.
Log Sources	Specify the full path of the single or wild card log file to be monitored in the Log Sources text box. Specific log file name patterns can be also specified. For example, to monitor the latest log files with names containing the string ais, the parameter specification can be /opt/RegexLog/Log Format file/ais_. Here, "" indicates leading/trailing characters (as the case may be). In this case, the eG agent first enumerates all the log files in the specified path that matches the given pattern, and then picks only the latest log file from the result set for monitoring.
Format file	Specify the full path of the single format file to be monitored in the Format File text box.
Dup Detection Key Attributes	Specify the case-sensitive comma-separated value of column names (for example - date, time) in the Dup Detection Key Attributes text box as mentioned in the respective Regex log file (.conf) and format file (.fmt). These column names will be used for detecting the duplicated lines in the log file.
Num events to catch up	This parameter is effective only when the agent is restarted. If you set this flag as NEW ROW, then the agent reads log from new row (line). If you set this flag as LAST PROC ROW ,then the agent reads log from the last processed row (line). By default, this flag is set as NEW ROW.
Event flood threshold	This parameter is effective only when the values set for Dup Detection Key Attributes parameter has some column names other than none as illustrated in the below example. Date, msg column names - Several number of rows in the log file will be detected based on these column names. When the default value for this parameter is set as send first, then the first row (line) among the detected rows will be considered as duplicate line.
Stateless alerts	Typically, the eG manager generates email alerts only when the state of a specific measurement changes. A state change typically occurs only when the threshold of a measure is violated a configured number of times within a specified time window. While this ensured that the eG manager raised alarms only when the problem was severe enough, in some cases, it may cause one/more problems to go unnoticed, just because they did not result in a state change. For example, take the case of the EventLog test. When this test captures an error event for the very first time, the eG manager will send out a CRITICAL email alert with the details of the error event to configured recipients. Now, the next time the test runs, if a different error event is captured, the eG manager will keep the state of the measure as CRITICAL, but will not send out the details of this error event to the user; thus, the second issue will remain hidden from the user. To make sure that administrators do not miss/overlook critical issues, the eG Enterprise monitoring solution provides the stateless alerting capability. To enable this capability for this test, set the STATELESS ALERTS flag to Yes. This will ensure that email alerts are generated for this test, regardless of whether or not the state of the measures reported by this test changes.
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.
Detailed Diagnosis	To make diagnosis more efficient and accurate, the eG Enterprise embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test for a particular server, choose the On option. To disable the capability, click on the Off option. The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled: The eG manager license should allow the detailed diagnosis capability Both the normal and abnormal frequencies configured for the detailed diagnosis measures should not be 0.

Measurements made by the test
Measurement	Description	Measurement Unit	Interpretation
Matched lines	Indicates the number of lines that were matched when compared with the format file (defined as a parameter in the Specific Test Configuration page).	Number	The detailed diagnosis of this measure lists the line number, message, custom slots, matched line, processing date and processing time.
Discarded lines	Indicates the number of discarded lines.	Number	It represents the number of lines that were not matched when compared with the format file.
Duplicate lines	Indicates the number of duplicate lines.	Number	Each line in the log file has unique keys based on the Duplicate Detection Key Attributes parameter. If the unique keys are identical with next matched line in the log file, then that next matched log lines are considered to be duplicate lines.
Total lines	Indicates the total number of lines.	Number	This mesaure represents the total number of lines that includes matched, duplicate and discarded lines.
Matched line rate	Indicates the rate at which the lines in the log file that were matched per minute.	Lines/min
Duplicate line rate	Indicates the rate at which the lines in the log file that were duplicated per minute.	Lines/min
Line rate	Indicates the rate at which the lines in the log file that were monitored per minute.	Lines/min