Viewing virtual application instance logs

You can view logs of virtual application instances.

1. Click Patterns > Virtual Application Instances.
2. Select a virtual application instance.
3. Click Manage in the toolbar.
4. Click the Logging tab.
   Logs are organized by virtual machine name, and each name contains the name of the role that is associated with the virtual machine. A role within a virtual application refers to the middleware that is installed and configured. For example, a virtual machine named application-was.11332975226124 contains was. This virtual machine has IBM® WebSphere® Application Server installed and configured.

   Note: The virtual machines in Stopped state are not displayed under the the Manage > Logging. Restart the virtual machines to view the entire list.

   Under each virtual machine in the list, logs are organized into sections, such as operating system log, logs for the type of middleware that is installed, pattern type plug-in log, and agent log.

   Attention: If you specified more log files or directories to monitor in the Logging Policy, these logs also display in this list.

   At the top of the list of virtual machines, you can specify a string to filter what files are displayed in the log viewer and then click Go. The filter can be prefixed by a tag that specifies one or more elements of the logs to be examined. The following tags are supported:

   role:

   The role name. For example, role:DB2 filters for role names that contain DB2.

   dir:

   The absolute path of the directory that contains the log. The filter searches the entire path for the specified file, but does not search within the log file name. For example, dir:var filters for directory paths that contain var.

   vm:

   The virtual machine name. For example, vm:application filters for virtual machine names that contain application.

   file:

   Log file name. For example, file:trace filters for file names that contain the word trace.

   The following usage rules apply to filters:

   • If a tag is not included in a search string, the file: tag is assumed.
   • Tag names are case-sensitive, but the filter string after the tag is not case-sensitive. For example, the string role:WAS matches a role name WAS and a role named was, but the string ROLE:was does not match anything because ROLE is not recognized as a valid tag.
   • You can apply multiple filters. For example, role:DB2,trace filters for logs with a name that contains trace, and that belongs to a role with a name that contains DB2.
5. To search the text of a log, click the log file name in the list and then click Search in the toolbar and specify the search criteria. You can use the Previous and Next commands in the toolbar to search for the next or previous occurrence of the last specified search string.
6. The following options are available to save logs:

   Download all log files

   When no filter is applied to the list of logs, or when the filter input box is cleared, you can click Download All to save an archived, compressed file, which contains all the logs on the virtual machine. If multiple virtual machines are displayed in the log viewer, a separate archive file is returned for each virtual machine.

   Download all files in a filtered list of logs

   When you enter a string into the filter box to select a subset of logs, you can click Download Filtered to download all of the files that are displayed in the filtered list as a single archive file.

   Download an individual log

   To save a specific log file, hover over the name of a log file in the list of logs and click the Download log icon that displays next to the name of the file. Alternatively, click the log file name and click the Save icon in the toolbar.