WebLogic

Background

The WebLogic Servers logs analysis App automatically Collect - Read - Parse - Analyzes - Reports all machine generated log data of the server and presents a comprehensive set of graphs and reports to analyze machine generated data. Use a predefined set of dashboards and widgets to  visualize and address the system software, code written, and infrastructure during development, testing, and production. This WebLogic logs analysis App helps measure, troubleshoot, and optimize your servers integrity, stability and quality with the several visualization and investigation dashboards.

Steps:

1. The WebLogic App is running on Base Domain, AdminServer, DefaultAuditRecorder, access and WFCA_Access standard logs.
   When adding/editing the logs to XpoLog it is mandatory to apply the correct log type(s) to each of the logs:

   1. weblogic - all logs that the application will analyze must have weblogic as a log type.

   2. basedomain - only the Base Domain logs must also be configured to have basedomain as a log type.

   3. adminserver - only the AdminServer logs must also be configured to have adminserver as a log type.

   4. audit - only the DefaultAuditRecorder logs must also be configured to have audit as a log type.

   5. access - only the Access and the WFCA_Access log must also be configured to have access as a log type.

   6. w3 - only the Access and the WFCA_Access log must also be configured to have w3 as a log type.
      
      
      

   
   
   

2. Once the required information is set, on each log click next and edit the log pattern, this step is crucial to the accuracy and deployment of the Linux App. Use the following patterns for each of the logs:
   
   

   1. Base_Domain:
      ####<{date:Date,MMM dd, yyyy hh:mm:ss a z}> <{priority:Priority,ftype=status;,TRACE;DEBUG;INFO;NOTICE;WARNING;ERROR;CRITICAL;ALERT;EMERGENCY}> <{text:Type,ftype=subsystem}> <{text:Machine_Name,ftype=machinename}> <{text:Server_Name,ftype=servername}> <{text:ThreadID,ftype=thread}> <{block,start,emptiness=true}<{block,end,emptiness=true}{text:UserID,ftype=username;,}>{block,start,emptiness=true}>{block,end,emptiness=true} <{text:Transaction_ID,ftype=transaction}> <{text:Diagnostic_Context_ID,ftype=diagcontext}> <{text:Raw_Time_Value,ftype=rawtime}> {block,start,emptiness=true}{regexp:Severity-Value,ftype=severityvalue;refName=Error Details,severity-value:\s([^\u005D]+).*}{regexp:RID,ftype=rid;refName=Error Details,rid:\s([^\u005D]+).*}{regexp:Partition-ID,ftype=partitionid;refName=Error Details,partition-id:\s([^\u005D]+).*}{regexp:Partition-Name,ftype=partitionname;refName=Error Details,partition-name:\s([^\u005D]+).*}<{text:Error Details,ftype=errordetails}> {block,end,emptiness=true}<BEA-{number:BEA,ftype=messageid}> <{string:Message,ftype=message}>{text}

   2. Admin_Server:
      ####<{date:Date,MMM dd, yyyy hh:mm:ss a z}> <{priority:Priority,ftype=status;,TRACE;DEBUG;INFO;NOTICE;WARNING;ERROR;CRITICAL;ALERT;EMERGENCY}> <{text:Type,ftype=subsystem}> <{text:Machine_Name,ftype=machinename}> <{text:Server_Name,ftype=servername}> <{text:ThreadID,ftype=thread}> <{block,start,emptiness=true}<{block,end,emptiness=true}{text:UserID,ftype=username;,}>{block,start,emptiness=true}>{block,end,emptiness=true} <{text:Transaction_ID,ftype=transaction}> <{text:Diagnostic_Context_ID,ftype=diagcontext}> <{text:Raw_Time_Value,ftype=rawtime}> {block,start,emptiness=true}{regexp:Severity-Value,ftype=severityvalue;refName=Error Details,severity-value:\s([^\u005D]+).*}{regexp:RID,ftype=rid;refName=Error Details,rid:\s([^\u005D]+).*}{regexp:Partition-ID,ftype=partitionid;refName=Error Details,partition-id:\s([^\u005D]+).*}{regexp:Partition-Name,ftype=partitionname;refName=Error Details,partition-name:\s([^\u005D]+).*}<{text:Error Details,ftype=errordetails}> {block,end,emptiness=true}<BEA-{number:BEA,ftype=messageid}> <{string:Message,ftype=message}>{text}

   3. DefaultAuditRecorder:
      First Pattern - #### Audit Record Begin <{date:Date,MMM dd, yyyy hh:mm:ss a}>  <Severity ={text:Severity,ftype=status}>  <<<Event Type = {text:Event Type,ftype=eventtype} ><Subject: {text:Subject,ftype=subject}{eol}>{regexp:ONCE,\u003CONCE\u003E}<<jndi>><type=<{text:jndi,ftype=type}>, application={text:Application,ftype=application}, path={text:Path,ftype=path}, action={text:Action,ftype=action}>{string:End Of Record} Audit Record End ####
      Second Pattern - #### Audit Record Begin <{date:Date,MMM dd, yyyy hh:mm:ss a}>  <Severity ={text:Severity,ftype=status}> <<<Event Type = {text:Event Type,ftype=eventtype}><Subject = Subject: {text:Subject,ftype=subject}{eol}{string:Principal,ftype=principal}>{string} type=<{text:jndi,ftype=type}>, {string:Message,ftype=message} Audit Record End ####

   4. Access:
      Default Pattern - {geoip:Client IP,ftype=remoteip} - {text:Remote User,ftype=remoteuser} [{date:Date,locale=en,dd/MMM/yyyy:HH:mm:ss z}] "{choice:Method,ftype=reqmethod;,GET;POST;HEAD} {url:URL,paramsFtype=querystring;ftype=requrl;paramsName=Query;,} {text:Request Protocol,ftype=reqprotocol;,}" {number:ResponseStatus,ftype=respstatus} {number:Bytes Sent,ftype=bytesent}{eoe}
      for more information see below the format Conversion Table:
      
      
      

      e. WFCA_Access

      Default Pattern - {geoip:ClientIP,ftype=remoteip}{tab}{ip:ServerIP,ftype= localip}{block,start,emptiness=true}:{number:ServerPort,ftype=serverport}{block,end,emptiness=true}{tab}{text:Remote User,ftype=remoteuser;,}{tab}{date:Date,yyyy-MM-ddHH:mm:ss;yyyy-MM-dd HH:mm:ss}{tab}{choice:Method,ftype=reqmethod;,GET;POST;HEAD}{tab}{url:URL,paramsFtype=querystring;ftype=requrl;paramsName=Query;,}{tab}{text:ResponseStatus,ftype=respstatus;,}{block,start,emptiness=true}{tab}{block,end,emptiness=true}{eoe}

      for more information see below the format Conversion Table: