Community
Participate
Working Groups
Currently the default time based correlator is matching events by exact time stamp. Time stamps are stored in the model as a double representing microseconds. Different log types contain time stamps having different time precision, some are recording time stamps with microseconds precision, others only with seconds etc. It would be nice to be able to customize the time based correlator so that the matching is done with a certain precision and/or granularity. Generally speaking we could say that an event e1 with time stamp t1 is correlated with an event t2 with time stamp t2 if and only if |t1-t2|<p where p is the precision or granularity set for the time correlator.
re-prioritize to P3, we should not use P4 or P5 as it basically implies it will never get done :-)
Currently, the time based correlation correlated using the exact time. The design for this feature require a Correlation page where the user can provide the time interval for matching two events. It also requires an extension point such that any correlation can contribute with it's own customizable preferences
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
See my comment Bug 87309#c12 for a usability suggestion.
*** Bug 87309 has been marked as a duplicate of this bug. ***
I was thinking first of an option in the correlation wizard, maybe a preference as well, and also an option to allow the user to change the correlation granularity in the log interactions view itself which would recorrelate the logs in the background and refresh the view. I am open to any other suggestions and I think we have to push this feature into 4.2.
Setting target to future so it doesn't show up in the 4.2 feature query.
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).
