Hi,
That is a bit of a complicated format. I suspect the problem with auto-detection here is that the log file does not contain a header and 'fields' definitions. Otherwise, it should really have been automatically detected as a W3C log file format.
Fortunately, as you indicated, the format is well defined.
You can parse this file using the PatternParser with the pattern:
%s{type} %d{yyyy-MM-ddTHH:mm:ss.ffffffZ} %s{elb} %s{client:port} %s{target:port} %s{request_processing_time} %s{target_processing_time} %s{response_processing_time} %s{elb_status_code} %s{target_status_code} %s{received_bytes} %s{sent_bytes} "%S{request}" "%S{user_agent}" %s{ssl_cipher} %s{ssl_protocol} %s{target_group_arn} "%S{trace_id}" "%S{domain_name}" "%S{chosen_cert_arn}" %s{matched_rule_priority} %s{request_creation_time} "%S{actions_executed}" "%S{redirect_url}" "%S{error_reason}" %s{target:port_list} %S{target_status_code_list} "%S{classification}" "%S{classification_reason}"%n
If you are not interested in all of the fields provided, I would recommend removing some of the column names. This will indicate to LogViewPlus that the data should be parsed, but not presented.
Hope that helps,
Toby