Command-Line Client Use Cases This command-line client is meant to enable use cases such as the following: ■ Using the log browser during headless automated testing. At whatever point is appropriate in your tests you can run a shell script that connects to a remote system, downloads certain types of logs and looks for patterns that indicate that failures or errors occurred. ■ Creating scripts of repeated actions. If you need to do a repeated sequence of actions on a given type of log, for example once for each of a number of different hosts, you can create a script that performs those actions for you, such as connecting to the host, downloading certain types of logs, and applying a filter to that log. ■ Using the log browser as a qualification tool for known defects. Log analysis is often the primary means of identifying defects. It would be helpful to quickly identify if a log bundle matches a pattern that corresponds to a known defect. The log browser command-line enables this sort of analysis. You can load the log bundle and then apply filters and search the log for matching entries. ■ Doing manual log analysis from the command line If the system in which you are doing log analysis is a purely command-line system, it is convenient to do log analysis activities like loading a log bundle, applying a filter and printing the results on the screen or to a file right from the command-line without needing to run any sort of GUI application.
