Quick Open Feature Behaviors
The Quick Open feature causes some changes in the way Message Analyzer behaves when dealing with different file types that contain data to be loaded. The following describes these behaviors when you are loading saved data from various supported file types into Message Analyzer:
Native parsed files — when you open a Message Analyzer Trace Parsed (.matp) file with the Quick Open feature, Message Analyzer automatically creates a new session tab for the default data viewer, for example, the Analysis Grid, which is then populated with the data from the specified .matp file. Message Analyzer names the session tab based on the default session name, which in this case would be the name of the saved .matp file. It also retrieves the session Description, which is accessible in the Edit Session dialog; you can display this dialog by clicking the Edit button in the Session group on the Ribbon of the Message Analyzer Home tab. Note, however, that Message Analyzer does not open the New Session dialog with the input .matp file listed on the Files tab of the dialog. This is the case because Message Analyzer can immediately display the data from a .matp file without any additional parsing.
Native unparsed files — when you open a Message Analyzer Trace Unparsed (.matu) file, Message Analyzer automatically creates a new session tab for the default data viewer, which is then populated with the data from the specified .matu file. Message Analyzer names the session tab based on the default session name, which in this case would be the name of the saved .matu file. It also retrieves the session Description, which is accessible as previously indicated. Note that Message Analyzer does not open the New Session dialog with the input .matu file listed on the Files tab of the dialog, but instead, automatically reparses the data from the .matu file and displays the results in the default data viewer. Because a reparse of the data is required for these file types, loading performance may decline somewhat, depending on the file size.
Native Network Monitor capture files — when you open a native Network Monitor capture (.cap) file, Message Analyzer automatically creates a new session tab for the default data viewer, as previously described, which is then populated with the data from the specified .cap file. Message Analyzer names the session tab based on the default session name, which in this case would be the name of the saved .cap file. However, if you previously added a session Description and saved the data from the file you are now loading, the session description text will not be persisted in the current Data Retrieval Session, as viewed from the Edit Session dialog.
Non-native files — when you open a Message Analyzer non-native file such as .log, .pcap, .pcapng, .csv, .tsv, .evtx, .etl, and so on, Message Analyzer automatically creates and names a new session tab for the default viewer based on the file name and loads the data without displaying the New Session dialog for further configuration. However, if you are opening a text log with a .log extension, Message Analyzer displays the New Session dialog to enable you to select a configuration file from the Text Log Configuration drop-down menu on the File tab, so that you can successfully parse the .log file.