Package: wls-analytics
$ wls-analyticsAdvanced Log Analysis for WebLogic Server ClustersIn the landscape of clustered WebLogic servers, managing and analyzing logs can pose a significant challenge. wls-analytics is a command-line tool that enables you to analyze logs from multiple WebLogic servers and domains. It is designed to be used by administrators and engineers who need to quickly identify and resolve issues in clustered WebLogic environments.wls-analytics offers a range of features tailored to the complexities of clustered WebLogic servers. It enables administrators and engineers to dissect logs within specific time intervals, construct efficient index files, and apply customizable patterns for data categorization.InstallationYou can install wls-analytics from PyPI as follows.$pipinstallwls-analyticsWhen you want to install from source, after you clone the repository, you can build the module as follows.$pipinstall--upgradesetuptoolswheel
$makebuildThe module package will be created under thedistdirectory. You can then install it as follows.pipinstalldist/wls_analytics-{version}-py3-none-any.whlPlease change the version of the module accordingly.Runwlsanalytics --helpfor details how to use the tool.FeaturesThere is a command to analyze SOA out logs. You can use it as follows.Set the home directory of the tool in theWLSA_HOMEenvironment variable.$exportWLSA_HOME=/path/to/wls-analyticsCreate the configuration file in$WLSA_HOME/config/config.yamland define the sets of log files the tool should analyze. Please checkconfig/config.yamlfor the sample configuration file.In the same configuration file, define the patterns to be searched in logs. There is already a number of patterns defined in the file. You can add your own patterns as well.Define the location of the configuration file in theWLSA_CONFIGenvironment variable. Alternatively, you can provide the path to the configuration file as an argument to the command.$exportWLSA_CONFIG=$WLSA_HOME/config/config.yamlRun the command to analyze the set of log files calledo2c. The set must be defined in the configuration file.$wlsanalyticssoaerroro2c--from"2023-09-19 11:06:39"--to"2023-09-19 12:06:39"There are various configuration options you can use. Runwlsanalytics soa error --helpfor details.As a result, you will get the following output:--Timerange:2023-09-1911:06:39-2023-09-1912:06:39
--Searchingfilesintheset'o2c'--Readingentriesfrom2files:83.6MB[00:07,12.4MB/s]--Completedin9.43s
TIMESERVERFLOW_IDCOMPOSITEERRORDETAIL2023-09-1911:06:51.875000soa_server11293508714SyncCustomerPartyListBRMCommsProvA…ERR_VALIDATION_FAILEDPCM_OP_UPDATE_CUSTOMER2023-09-1911:07:33.145000soa_server11293447650SyncCustomerPartyListBRMCommsProvA…ERR_VALIDATION_FAILEDPCM_OP_UPDATE_CUSTOMER2023-09-1911:08:02.565000soa_server11293525804SyncCustomerPartyListBRMCommsProvA…ERR_VALIDATION_FAILEDPCM_OP_UPDATE_CUSTOMER
...When you use the index option--index, there will be an index created for the output. You can then use to explore log entries that belong to specifc error by using the index value.wlsanalyticssoaindextevuThis will open thelessviewer on your local computer with the entries that belong to the error with the index valuetevu.