Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 164424

Summary:	"Show correlated log records only" has no effect in Log View
Product:	z_Archived	Reporter:	Dave Smith <smith>
Component:	TPTP	Assignee:	Alex Nan <apnan>
Status:	CLOSED FIXED	QA Contact:
Severity:	major
Priority:	P1	CC:	ewchan, jkubasta
Version:	unspecified	Keywords:	plan
Target Milestone:	---
Hardware:	PC
OS:	Windows 2000
Whiteboard:	closed460

Description Dave Smith

2006-11-14 00:26:28 EST

I imported Apache access and error logs and correlated them based on time.  I opened the correlation in the Log View and then applied the "Show correlated log records only" filter in the log view.  It had no effect.  All of the log records from both log files were shown in the Log View.  Applying the filter in the Log Interactions view caused only the correlated log records to be displayed.

I was testing the 4.3 i3 200611070100 driver on Windows 2000 with IBM 1.4.2 JRE.

Comment 1 Eugene Chan

2006-11-14 09:57:15 EST

Currently, "Show correlated log records only" is only applicable in Interaction views.

Comment 2 Alex Nan

2007-01-12 15:18:15 EST

Show correlated events doesn't make too much sense in the log view, unless you have a correlation container proxy opened, but still in this case the user cannot figure out which record to which record is correlated. In the old tree viewer like log view we were dislaying correlated events of an event. A solution would be to have the associated events tab displaying the associated events events as hypelinks, so that clicking on a hyperlink would select the corresponding event in the view. 
If the input to the log view is not a correlation container proxy then the actions should be either greyed out or rather not displayed.

Comment 3 Alex Nan

2007-01-12 15:19:33 EST

Rough estimate 18h, including the displaying of associated CBE events in the Associated events tab.

Comment 4 Alex Nan

2007-04-27 01:22:39 EDT

I have removed the Show correlated... menu from the log view, which is not applicable.

Comment 5 Paul Slauenwhite

2009-06-30 09:52:15 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 this 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.