Supported Since: 17.01
Each active ESB instance in the cluster publishes its logs to the IPS database. The logs can be viewed in different contexts for checking ESB health and troubleshooting issues.
Click UltraESB Logs on the left navigation bar.
Logs are paginated, and by default the latest set of logs is loaded so as to provide a quick insight into the latest events taking place in the instance.
Logs can be filtered in different perspectives:
Timespan of logs
Live pod filter: enabling this filters out all non-running pods; useful when, even with the rest of the filters applied, the result contains logs from a large number of inactive ('dead') pods
Name of the cluster to which the instance belongs
Server name (e.g.
Server-1) in case of multiple replications in the cluster
Pod name: Kubernetes identifier for the pod
Different combinations of the above filters can be utilized for narrowing down the extent of retrieved logs.
Some log filters are interdependent such that the available options for one is controlled by the selection made on the other. For example, modification of timespan, live pod option or cluster name would restrict available options for all of the other fields.
Columns drop-down can be used to decide the table columns to be be displayed.
Ordering of logs (ascending <img>/descending <img>/unsorted) based on a column can be controlled by clicking on the respective column header repeatedly.
Logs currently being displayed can be saved as a CSV file using the Download button.
Navigate to Details view of the desired project version.
Click Logs on the vertical tab navigation menu.
A Log Viewer will appear, pre-filtered for the specific project version. Other filters will be automatically updated to reflect possible filter options, e.g. cluster filter will only display names of clusters where the project version has been deployed at least once.