The first time you open a log file in LogViewPlus you may be presented with the dialog above explaining that the Basic Parser has been used to process the given log file. The dialog reads:
"LogViewPlus was unable to find a parser mapping for this log file and used the default Basic Parser. This parser can be inefficient and some columns may not be shown. For better results, please configure a parser."
This isn't necessarily a bad thing. The BasicParser is functional and may provide you with all the features you need for your current task - with zero configuration. However, you are usually better off if you use one of the more specialized parsers. This is especially true for log files you open frequently as the specialized parsers offer more functionality and better performance. Configuring Log Parsers manually was covered in the previous section.
If you decide that the Basic Parser is appropriate for your use case, you can simply click the 'Use Basic Parser' checkbox followed by 'OK'. This will add an explicit parser configuration for the Basic Parser which will prevent this dialog from being shown in the future.
If you decide to configure a parser, we recommend using the Parser Wizard. The Parser Wizard can be opened from the Settings -> Parser Mappings view, but a better option is to run the Parser Wizard directly from the Basic Parser Detected dialog. Executing the Parser Wizard in this way has the advantage of populating a few fields in advance such as sample log entries.