Community
Participate
Working Groups
1. open log import wizard 2. select Common base event xml log as the log type 3. type in a path pointing to an apache access log 4. the wizard imports the access log without showing any error, no error gets logged in the log either, but the log view is empty.
Target 4.4i3 for now.
defect not yet triaged. Need to see if we can contain in 4.4
Alex, does this need to be deferred due to PII dates?
defer since PII cutoff has passed
Here are some usability comments from Hendra Suwanda that include other changes related to this defect. They were originally posted to 135531. 135531 covered changes to GLA required to detect an invalid log. It will be closed. This defect will be used to fix the UI side of this problem. Two comments from usability point of view: 1. The error message is intended for the programmer (not for the end-user). It says something about "parsing error" (not very useful to the end-user). I have to go through "Details >>" to notice that indeed the log file type may be incorrect. Please make sure that the error message is intended for the end-user, not the implementor. 2. Although there was an error in the import process and no record was imported, the log entry is created in the navigator view. I suggest that either a "red x" error icon be displayed as a decorator for that entry, or do not create the entry in the first place (since 0 record was imported).
Adding people cc'ed on 135531
This is required from AC perspective.
Alex, is this containable in 4.4.1? If not, please size. Thanks.
No support will be provided for the Log and Trace Analyzer post 4.5.
Closing.
