Bug 62351 - Allow symptom databases to be associated with logs or other resources
Summary: Allow symptom databases to be associated with logs or other resources
Status: CLOSED WONTFIX
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: TPTP.monitoring (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 2000
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Alex Nan CLA
QA Contact:
URL: http://www.eclipse.org/tptp/groups/Ar...
Whiteboard:
Keywords: Documentation, ui
Depends on:
Blocks:
 
Reported: 2004-05-14 16:14 EDT by Navid Mehregani CLA
Modified: 2010-06-03 15:08 EDT (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Navid Mehregani CLA 2004-05-14 16:14:39 EDT 
Problem:
   Go to Hyades logging examples and create two copies of the 'Apache log 
   correlation/Analyzer Sample' with different project names -> In the 
   log navigator view -> select the error log file -> right click on one of the
   records -> analyze all -> default log analyzer -> select analysis result.  
   For one of the error log files notice that the analysis is repeated more 
   than once in the
Comment 1 Eugene Chan CLA 2004-05-19 23:19:35 EDT 
This is because 2 symtom DBs was created which were used for analyze, and the 2 
symtom DB happened to have same content in this case.
Comment 2 Navid Mehregani CLA 2004-05-20 10:24:46 EDT 
As discussed with Eugene, right now there is no way to associate a symptom
database with a specific project (i.e. If a symptom database exists in one
project, it will be used by all projects in the workspace).  I've re-opened this
bug and specified the severity as 'enhancement'.  I think we should eventually
provide the users with the functionality of associating a symptom database with
a specific projects.
Comment 3 Ruth Lee CLA 2005-02-09 17:18:05 EST 
Adding Hendra Suwanda to the CC list because Navid has gone back to school. If
you have any questions about these defects then please ask Hendra.
Comment 4 Ruth Lee CLA 2005-07-12 10:56:03 EDT 
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
Comment 5 Valentina Popescu CLA 2005-10-28 12:34:55 EDT 
update component
Comment 6 Valentina Popescu CLA 2005-11-24 15:55:28 EST 
update version
Comment 7 Dave Smith CLA 2005-12-07 11:10:03 EST 
Candidate for 4.2
Comment 8 Navid Mehregani CLA 2005-12-07 11:14:15 EST 
The posted URL doesn't seem to be working Dave.
Comment 9 Dave Smith CLA 2005-12-07 13:49:45 EST 
Removing from the 4.2 candidate list due to lack of resources.
Comment 10 Dave Smith CLA 2006-01-25 12:23:07 EST 
Setting target to future so it doesn't show up in 4.2 feature query.
Comment 11 Alex Nan CLA 2007-08-14 17:14:55 EDT 
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.
Comment 12 Alex Nan CLA 2008-06-24 18:13:48 EDT 
Closing.
Comment 13 Paul Slauenwhite CLA 2009-06-30 06:46:52 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).