WSO2 ESB Monitoring – logs, tail, file size

Logs

In wso2 esb there are different kind of log file that help you to audit services.

Before view log files you can set logging in your proxy services, in here you can use full logs or your own custom log.

Also you can enable statistics and enable tracing in the service level. To do that , List > specific service > enable tracing/enable statistics.

For that refer this link,

https://docs.wso2.com/display/ESB481/Log+Mediator

Now you can view logs. For that go <wso2Home>/repository/logs

Here simple description about each log file type,

·         http_access_management_console.log – this file logs about all https calls. Mainly about management console get and post calls.

·         Wso2carbon.log – this is the mail log file of wso2 esb. In here you can find all information regarding the system. As I previously mentioned, if you set logs in your proxy service, you can view thos logs in here. **** Keep remind that if you use full log in your proxy service, .log file may become bigger. So keep track these files. Also there is a feature inbuilt that will version all log files daily.

·         Patches.log – using this you can find all patch information.

·          Wso2_esb-errors.log – you can find all error messages in this place.

·         Wso2_esb_service.log – in here you can find all service invocations. Information about called services.

·         Wso2_esb_trace.log – as I mentioned previously, if you were activated tracing you can find all service traces, how the mediation flow going, who invoked services (client ips), what are the endpoints called. 

If you are using linux, you can tail your log files using tail command, this will help you to audit in an efficient way. To use tail use like below,

>tail -1000f  <esbHome>/repository/logs/wso2carbon.log

Also if you are using jconsole, remember to keep in touch with memory usage. It will show the sequence of memory usage and other all server information.