Splunk Search

How can I report on all of those thousands of BEA- messages in our weblogic logs?

Rob_Jordan
Explorer

How can I report on all of those thousands of BEA- messages in our weblogic logs?

Tags (2)
0 Karma
1 Solution

Rob_Jordan
Explorer

These searches will extract BEA- messages from the logs and report by message number

Example of a BEA Message:

####<Jan 1, 2009 2:34:07 PM CDT> <Error> <WebLogicServer> <hostname> <managedserver> <[ACTIVE] ExecuteThread: '8' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1273606447204> <BEA-000337> <[STUCK] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)' has been busy for "715" seconds working on the request

Use a regular expression to extract a custom field called BEA_MSG_NO

"<BEA-"|rex field=_raw "(?<BEA_MSG_NO>BEA-\d\d\d\d\d\d)"|stats count by BEA_MSG_NO

"<BEA-"|rex field=_raw "(?<BEA_MSG_NO>BEA-\d\d\d\d\d\d)"|timechart count by BEA_MSG_NO

"<BEA-"|rex field=_raw "(?<BEA_MSG_NO>BEA-\d\d\d\d\d\d)"|top BEA_MSG_NO limit=10000

NOTE: if you prefix your search with the sourcetype for your weblogic logs, your results should come back much faster.

sourcetype="*weblogic.out*" "<BEA-"|rex field=_raw "(?<BEA_MSG_NO>BEA-\d\d\d\d\d\d)"|stats count by BEA_MSG_NO

sourcetype="*weblogic.out*" "<BEA-"|rex field=_raw "(?<BEA_MSG_NO>BEA-\d\d\d\d\d\d)"|timechart count by BEA_MSG_NO

sourcetype="*weblogic.out*" "<BEA-"|rex field=_raw "(?<BEA_MSG_NO>BEA-\d\d\d\d\d\d)"|top BEA_MSG_NO limit=10000

View solution in original post

0 Karma

Rob_Jordan
Explorer

These searches will extract BEA- messages from the logs and report by message number

Example of a BEA Message:

####<Jan 1, 2009 2:34:07 PM CDT> <Error> <WebLogicServer> <hostname> <managedserver> <[ACTIVE] ExecuteThread: '8' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1273606447204> <BEA-000337> <[STUCK] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)' has been busy for "715" seconds working on the request

Use a regular expression to extract a custom field called BEA_MSG_NO

"<BEA-"|rex field=_raw "(?<BEA_MSG_NO>BEA-\d\d\d\d\d\d)"|stats count by BEA_MSG_NO

"<BEA-"|rex field=_raw "(?<BEA_MSG_NO>BEA-\d\d\d\d\d\d)"|timechart count by BEA_MSG_NO

"<BEA-"|rex field=_raw "(?<BEA_MSG_NO>BEA-\d\d\d\d\d\d)"|top BEA_MSG_NO limit=10000

NOTE: if you prefix your search with the sourcetype for your weblogic logs, your results should come back much faster.

sourcetype="*weblogic.out*" "<BEA-"|rex field=_raw "(?<BEA_MSG_NO>BEA-\d\d\d\d\d\d)"|stats count by BEA_MSG_NO

sourcetype="*weblogic.out*" "<BEA-"|rex field=_raw "(?<BEA_MSG_NO>BEA-\d\d\d\d\d\d)"|timechart count by BEA_MSG_NO

sourcetype="*weblogic.out*" "<BEA-"|rex field=_raw "(?<BEA_MSG_NO>BEA-\d\d\d\d\d\d)"|top BEA_MSG_NO limit=10000
0 Karma
Get Updates on the Splunk Community!

AppDynamics Summer Webinars

This summer, our mighty AppDynamics team is cooking up some delicious content on YouTube Live to satiate your ...

SOCin’ it to you at Splunk University

Splunk University is expanding its instructor-led learning portfolio with dedicated Security tracks at .conf25 ...

Credit Card Data Protection & PCI Compliance with Splunk Edge Processor

Organizations handling credit card transactions know that PCI DSS compliance is both critical and complex. The ...