IBM WebSphere AS

Displays events from the IBM WebSphere Application Server (WAS) logs, containing the string, WSVR0220I.

This search can be useful to find errors that occurred when the application stopped responding abruptly.

Included in dashboard: No

Displays events from the WAS logs, containing the string, SECJ0118E.

This search can be useful to find authentication errors that might occur when the system does not recognize the user credentials provided for logon.

Included in dashboard: Yes

Displays events from the WAS logs, containing the string, WSVR0501E.

This search can be useful to find errors that occur when the WebSphere Application Server does not initialize even after starting it.

Included in dashboard: Yes

Displays events from the WAS logs, containing the string, WSVR0605W.

This search can be useful to find errors that occur when the threads in the server are hung (or not working).

Included in dashboard: No

Displays events from the WAS logs, containing the string, ADMS0015E.

This search can be useful to find errors that occur when the node agent cannot connect to the deployment manager.

Included in dashboard: No

Displays events from the IBM WebSphere Application Server logs, containing the string, WSVR0221I.

This search can be useful to find messages related to starting the application console.

Included in dashboard: No

Displays events from the WAS logs, containing the string, WSVR0220I.

This search can be useful to find messages related to stopping the application console.

Included in dashboard: No

Displays events from the WAS logs, containing the string, (GET && (404 || 501 || 401 || 500)) || (POST && (404 || 501 || 401 || 500)).

Number of transactions (GET/POST) which is failing e.g. 404, 401, 500, etc. in HTTP Access Log

Included in dashboard: No

Displays events from the WAS logs, containing the string, TCPC0003E.

This search can be useful to find errors related to starting the application server in the scenario of a TCP port conflict.

Included in dashboard: No

Displays events from the IBM WebSphere Application Server logs, containing the string, WSVR0001I.

This search can be useful to find errors related to starting the application server.

Included in dashboard: Yes

Displays events from the IBM WebSphere Application Server logs, containing the string, WSVR0024I.

This search can be useful to find errors related to stopping the application server.

Included in dashboard: Yes

Helps index and structure the access logs.

It can be useful to troubleshoot general problems, performance problems, security problems, and so on.

Helps index and structure the error logs.

It can be useful to troubleshoot general problems, performance problems, security problems, and so on.

Helps index and structure the native_stderr logs.

It can be useful to troubleshoot various problems related to native code such as memory usage errors.

Helps index and structure the native_stdout logs.

It can be useful to troubleshoot various problems related to native code such as memory usage errors.

Helps index and structure the SystemErr logs.

It can be useful to troubleshoot problems related to starting or stopping the application server process such as the application server, node agent, and deployment manager.

Helps index and structure the SystemOut logs.

It can be useful to troubleshoot problems related to starting or stopping the application server process such as the application server, node agent, and deployment manager.

Helps index and structure messages from the wsadmin.traceout log file.

It can be useful to troubleshoot system management problems.

Provides a summary of the following errors related to the proper running the application server.

• Errors related to starting the application server
• Errors related to stopping the application server
• Errors related to authentication (logging on)
• Errors related to initializing the application server