Filtering admin log entries in the web user interface

You can filter the admin log entries that are displayed in the App Connect Enterprise web user interface.

Before you begin

Read the following topics:

About this task

You can apply filters to control the set of events that are displayed in the web user interface, by entering a search string. You can include one or more tags in the search string, and use exact matching, wildcards, and full regular expressions.

For example, if you want to find all entries that relate to a message flow called myAsyncRequestResponseFlow, you can enter the MSGFLOW: tag followed by the name of the message flow in the search field: 
MSGFLOW:myAsyncRequestResponseFlow

As a result of this search, the entries are filtered to display only the activities that were carried out against the myAsyncRequestResponseFlow message flow.

You can use the * wildcard character to represent a tag with any value (a tag must be present but it can have any value). For example, to find out details of the BAR file in which the message flow was deployed, you can filter the entries to show all events that relate to the specified message flow and that also contain a BAR_FILE: tag: 
MSGFLOW:myAsyncRequestResponseFlow BAR_FILE:*

The resulting filtered list displays only events relating to the myAsyncRequestResponseFlow message flow, including details of the BAR file in which it was deployed.

You can also use regular expression syntax in the search string to set patterns for matching the entries required. For example, to display all the deploy events that have occurred as a result of the mqsideploy command being run, you can search for matches to the REQUEST_ID: tags that include mqsideploy, preceded by a regular expression .* to match the timestamp prefix, and followed by .* to match the process ID suffix. By also including the HTTP_METHOD tag that matches POST, only the event that occurs when the command is run is displayed, and not all the events relating to the deployment resource changes that result from the deploy:
REQUEST_ID:.*mqsideploy.* HTTP_METHOD:POST