Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 111016 - Provide indexing support for the log analysis engine
Summary: Provide indexing support for the log analysis engine
Status: CLOSED INVALID
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: TPTP (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 2000
: P1 enhancement with 1 vote (vote)
Target Milestone: ---   Edit
Assignee: Alex Nan CLA
QA Contact:
URL: http://www.eclipse.org/tptp/groups/Ar...
Whiteboard: closed460
Keywords:
Depends on:
Blocks:
 
Reported: 2005-09-28 20:57 EDT by Alex Nan CLA
Modified: 2016-05-05 10:51 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alex Nan CLA 2005-09-28 20:57:04 EDT
In the current implementation the log analysis engine is doing a "brute force" 
pattern matching when analyzing log files against symptom databases, i.e. it's 
matching each symptom pattern to each log record message. The analysis  running 
time can be reduced if a text index would be created and queried. Also using a 
more efficient pattern matching algorithm (Boyer-Moore for example), currently 
Java String indexOf is used to verify if a pattern is matching a string, would 
improve the overall performance of the log analysis engine.
Comment 1 Valentina Popescu CLA 2005-09-29 09:52:04 EDT
Do you plan to hav ethis done in 4.1 ? If not please change the target/ 
severity ( should this be an enhancement ? )
Comment 2 Alex Nan CLA 2005-09-29 10:25:08 EDT
No, not in 4.1, I was thinking of 4.2. Yes, it is supposed to be a feature.
Comment 3 Valentina Popescu CLA 2005-11-10 11:55:29 EST
Theme: Scaling Up
Comment 4 Valentina Popescu CLA 2006-02-10 12:18:32 EST
Setting target to future so it doesn't show up in the 4.2 feature query.
Comment 5 Valentina Popescu CLA 2006-06-26 19:31:04 EDT
The current analysis engine uses the fastXPath engine for log analysis 
Please reopen if this request is still valid
Comment 6 Paul Slauenwhite CLA 2009-06-30 06:30:28 EDT
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).
Comment 7 Paul Slauenwhite CLA 2009-06-30 10:33:45 EDT
As of TPTP 4.6.0, TPTP is in maintenance mode and focusing on improving quality by resolving relevant enhancements/defects and increasing test coverage through test creation, automation, Build Verification Tests (BVTs), and expanded run-time execution. As part of the TPTP Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes), this enhancement/defect is verified/closed by the Project Lead since the originator of this enhancement/defect has an inactive Bugzilla account and considered to be fixed. If this enhancement/defect is still unresolved and reproducible in the latest TPTP release (http://www.eclipse.org/tptp/home/downloads/), please re-open.