Community
Participate
Working Groups
Many log files contain header records that include data that pertains to the following records. The GLA parser needs to have the ability to cache some or all of the header record data so that it can be used to parse subsequent event records. Here is an example of some log data: Wed Sep 18 20:36:33 2002 20:36:33 Event alarms enabled. ALARMPROG = '/work/informix940/etc/log_full.sh' 20:36:33 Booting Language <c> from module <> 20:36:33 Loading Module <CNULL> 20:36:33 Booting Language <builtin> from module <> 20:36:33 Loading Module <BUILTINNULL> 20:36:38 Informix Dynamic Server Version 9.40.UN318 Software Serial Number AAA#B000000 20:36:40 Attempting to bring listener thread down. 20:36:40 Server stopped. 20:36:40 Informix Dynamic Server Stopped. 20:36:40 mt_shm_remove: WARNING: may not have removed all/correct segments 20:38:22 Informix Dynamic Server Started. 20:38:22 Requested shared memory segment size rounded from 8000KB to 8192KB Wed Sep 18 20:38:22 2002 20:38:22 Event alarms enabled. ALARMPROG = '/work/informix940/etc/log_full.sh' 20:38:22 Booting Language <c> from module <> 20:38:22 Loading Module <CNULL> 20:38:22 Booting Language <builtin> from module <> 20:38:22 Loading Module <BUILTINNULL> 20:38:27 Informix Dynamic Server Version 9.40.UN318 Software Serial Number AAA#B000000 20:38:27 Attempting to bring listener thread down. Header records contain the full date/time but the subsequent event records only contain times. The rules writer should be able to configure the Parser to cache the date from the header records and use it in the rules for creationTime to specify a complete timestamp.
This is a high priority feature as it affects many log types. This functionality is not available in the current rules parser and a user must write a static parser to handle the header record data. Theme: Primary - Simple to use Secondary - Broader Community Parser writers can write regular expressions to parse the logs instead of writing static parser classes. More log types can be parsed with rule-based adapters.
This requirement comes from IBM AC group.
Because this feature requires Parser schema changes, it affects the API.
Deferring from 4.1 as per the official 4.1 enhancement plan. http://eclipse.org/tptp/home/project_info/featureplans/features.php?source=All&project=All&release=4.1&file=TPTPFeatures_4.1.xml
Would like to see this considered for 4.2 as it is an important feature for parser writers.
Candidate for 4.2
Removing from the 4.2 candidate list due to lack of resources.
Setting target to future so it doesn't show up in 4.2 feature query.
Please set priority to P3, no longer high priority
Due to lack of resources this enhancement request is resolved as WONTFIX. Please feel free to reopen if you consider it's a required enhancement.
Closing.
As of TPTP 4.6.0, TPTP is in maintenance mode and focusing on improving quality by resolving relevant defects and increasing test coverage through test creation, automation, Build Verification Tests (BVTs), and expanded run-time execution. As such, TPTP is not delivering enhancements. As part of the TPTP Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes), this enhancement is resolved as WONTFIX. For this enhancement to be considered, please re-open with an attached patch including the Description Document (see http://www.eclipse.org/tptp/home/documents/process/development/description_documents.html), code (see http://www.eclipse.org/tptp/home/documents/resources/TPTPDevGuide.htm), and test cases (see http://www.eclipse.org/tptp/home/documents/process/TPTP_Testing_Strategy.html).
