What is new for troubleshooters

This topic highlights new and changed features for troubleshooting and servicing the product, with a focus on the ability to automatically detect and recover from problems.

  • [8.5.5.16 or later]Analyzing WebSphere Application Server logs with Elastic Stack

    Run WebSphere Application Server with logging for the JSON format in the console to break down log events into fields and store them in Elasticsearch. Then, use Kibana to monitor multiple WebSphere Application Server pods with dashboards and search, or filter log records with queries.

  • [8.5.5.16 or later]LogViewer command-line tool

    Use the -maxFileSize and -maxFiles parameters to enable file rollovers, so that the LogViewer saves only the latest output logs. Use the -resumable and -resume parameters to save the location of already processed log records and to resume processing from the last saved location. Use the -format json option to format output in JSON to enable you to easily feed log content to log analysis tools.

  • [8.5.5.15 or later]Collecting troubleshooting data with diagnostic plans

    Use diagnostic plans to help diagnose intermittent or long-lasting problems in WebSphere Application Server. With a properly configured diagnostic plan, an application server can respond automatically to an anticipated problem and produce the wanted traces and Java dumps.

  • [8.5.5.12 or later]Troubleshooting long running JDBC transactions

    Use the enableJDBCTiming and disableJDBCTiming MBean operations to investigate long running JDBC transactions. These operations enable and disable the timing of transactions, and the output of trace and debug information.