Monitor Server Logs

ConnectALL can monitor server logs to assist in monitoring and managing of the various connections it governs. To monitor a server log, click the Monitor Server Log link at the bottom of the page or select the Monitor Logs menu. The user is always expected to select from a drop down and can search the specific pattern by using Advanced configuration.


Note

Admin users can access the logs related to the app-links in the group they belong to, and will be able to view the Mule Logs. However, the CATomcat logs will not be visible to an admin user.


Any log file name that is selected from Log File Path will bring up the Server Logs window.  Filename patterns defined int he ConnectAll.properties is based on regular expressions.

Default Configuration is given below.

 

mule.logfile.pattern=mule-app-ConnectAll*
tomcat.logfile.pattern=connectall*

Advanced Configuration

Advanced Configuration allows a user to modify and override the property configuration from the UI. Changes in the Advanced Configuration are session scoped. File Name Filter pattern must be given as regx pattern. The default fetch log size is 10, can be changed in the UI.


There is a Pause Logs button at the bottom. Allowing the log to be paused.


Configuration Routine for on-demand user information tracking in the Apache Tomcat Access Logs:

1. Place the connectallvalve.jar in the Apache Tomcat System Library.
2. Navigate to the 'conf' directory in the tomcat location and open the server.xml
3. Search for the element <host> and the sub-element <valve>. In the "valve" element, You can use the Pattern Value separated by space. Values for the pattern attribute are made up of literal text strings, combined with pattern identifiers prefixed by the "%" character to cause replacement by the corresponding variable value from the current request and response. The following pattern codes are supported:

%a - Remote IP address
%A - Local IP address
%b - Bytes sent, excluding HTTP headers, or '-' if zero
%B - Bytes sent, excluding HTTP headers
%h - Remote hostname (or IP address if enableLookups for the connector is false)
%H - Request protocol
%l - Remote logical username from identd (always returns '-')
%m - Request method (GET, POST, etc.)
%p - Local port on which this request was received. See also %{xxx}p below.
%q - Query string (prepended with a '?' if it exists)
%r - First line of the request (method and request URI)
%s - HTTP status code of the response
%S - User session ID
%t - Date and time, in Common Log Format
%u - Remote user that was authenticated (if any), else '-'
%U - Requested URL path
%v - Local server name
%D - Time taken to process the request, in a millisecond
%T - Time taken to process the request, in seconds
%F - Time taken to commit the response, in a millisecond
%I - Current request thread name (can compare later with stack traces)

Note: For ConnectALL Username to be printed in the localhost Access Logs, use the %u pattern.

4. In the same above "valve" element, replace the existing class name as "com.connectall.custom.valve.ConnectAllLogAccessValve"
5. Goto ConnectAll.properties. Set the property as ca.user.track.handle=true which will be loaded into CA Code, by default this will be 'false'.
6. Restart the TOMCAT server.

View Audit Logs

The ConnectAll_Audit log file is another log file available under the Tomcat Log file type. To access the ConnectAll_Audit log file:

  1. Select Tomcat in the Log File Type drop-down list.
  2. Select 'ConnectAll_Audit.log' from the Log file path drop-down list.
  3. Select Info in the next drop-down list.
  4. Click Play. 

The log file will be displayed. The log file records the following activities:

  • Creating app-link
  • Modifying app-link
  • Enable app-link
  • Disable app-link
  • Delete app-link
  • Clone app-link
  • User Management activities (Users tab and Groups tab).