By default there is no such view. There are at least 2 potential solutions, that you could use, but your workaround might be easier ;-) :
- Enable Runtime Messages
In the web console go to Troubleshooting > Runtime Messages > Runtime information.
Enable Info
level, save and restart. Then you will be able to filter massages using filter in the table and providing message fragment.
- Use HPEL logging and filtering
You can switch default logging to HPEL in the Logging and tracing > server1 > Switch to HPEL
. After that your logging will be done in binary form (much better performance) and you will be able to do searches based on the event code, message content etc. You will be able to view log either from the console Logging and tracing > server1 > JVM Logs > Runtime
with search/filtering capability, or from command line using logviewer
tool. Tool can be used a bit like tail/grep combination and print only relevant information or information from specified application. In this case you will also be able to view past events also, as in Runtime messages you see only events from server startup.
- Custom MBean listener
You could write code to listen on events generated by the server, but probably too much effort for your need.
See also: