Community
Participate
Working Groups
The usual scenario for a support person who would make use of the LTA capabilities to analyze and correlate logs is to start with a zip containing multiple log files. The current UI metaphor forces him to : 1. unzip the file 2. go to File>Import Log action then for every file open the Add Log wizard, select the log, the type of log, version, etc The user needs to be able to point to the zip file and have a 'Open with LTA' option. The open action will break the zip, read the logs and based on the log file names make a guess on the log type ( the log version is usually stored in the log file so the action can get this information as well ) After the zip is processed, the import log wizard opens. It shows a new log set based on the zip file name ( at this point some validation for unique log sets is required, ie if there already is a log set with this name, then verify if the content has been changed and prompt the user to rename. override the existing log set ). The log files for which the type and version has been successfully identified are displayed, as well as the ones that could not be identified. For those ones an error message icon is displayed and the user cannot finish the dialog unless it manually enter these log files type/version or removes the log from the list. Once the user enter a type and version for a log file, this information will be stored in the registry so that these values will be used next time a file with the same name is part of a zip. Note that this import utility should accept zipped logs as well as multiple log file selections ( in this case the action should be available only when the selected file have the extension .log )
"The open action will break the zip, read the logs and based on the log file names make a guess on the log type ( the log version is usually stored in the log file so the action can get this information as well )...Note that this import utility should accept zipped logs as well as multiple log file selections ( in this case the action should be available only when the selected file have the extension .log )" This function should be designed as a part of an import service which is completely independent of the UI so it can be used as a web service. The result should include all of the details needed to import each file in the request. This result should then be processed by the UI and in the eclipse case, log sets created, etc.
Candidate for 4.2
approved by the PMC group to be moved to a higher release
Moving to future for now so it doesn't show up in the 4.2 queries.
please close this - no longer relevant
Hello, meaning it is fixed or it is not the proper bugzilla to track the issue ? :)
Remove plan keyword since this is not in plan for the upcoming 4.3 release
Valentina,Meaning it is fixed ? Or we will not do it ? This is important for usability to be bale to import the zip in one shot and read a possibly associated metadata to understand what log parser to use... :) Let me know
No, it was not fixed yet The plan keyword is used to mark features planned to be done in the current release ( 4.3 ); unfortunately this is not one of the requestes that made the plan. I agree with you that this is a required usability enhancement but there were some other features with higher priority that were included into the plan. The plan has been build based on community input (voting - 0 votes for this feature) and available resources.
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.
Important: required Enhancement
This is not required from the AC perspective.
No support will be provided for the Log and Trace Analyzer post 4.5.
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).
