Transact

  1. Home
  2. Transact
  3. Features and Functions
  4. Administrator Role and Features
  5. System Configuration
  6. Log Monitoring Tool

Log Monitoring Tool

Ephesoft Transact now offers a new system of alerts. All alerts are handled by the Log Monitoring Tool, which has been created specifically for this purpose.

The tool is responsible for monitoring application logs and generating alerts on the basis of the following factors:

Log eventsthe tool keeps record of log events and alerts the system administrator if the log event is not received within a predefined timeframe
Log sizethe tool monitors the size of the log generated by the application and alerts the system administrator if the log size crosses a predefined threshold
Log folder sizethe tool monitors the size of the application log folder and alerts the system administrator if the log folder size crosses a predefined threshold
Log folder disk sizethe tool monitors the size of the disk which contains the log folder and alerts the system administrator if the disk size crosses a predefined threshold
Connection timeoutthe tool alerts the system administrator if connection to the server cannot be established within a predetermined timeframe
Connection errorthe tool alerts the system administrator if connection to the server cannot be established due to an incorrect configuration
IO exception errorthe tool alerts the system administrator if an error occurred while trying to monitor the log folder (e.g. when the application does not have access to the log folder)

All alerts are sent via email.

The Monitoring Tool should be executed by the system administrator. It requires access to TCP ports and needs permission to read the size of the log folder and associated hard disk.

The tool is designed to monitor one server only. By default, it is located in the monitoring-tool subfolder of the Ephesoft application folder.

C:UsersEphesoftAppDataLocalMicrosoftWindowsINetCacheContent.WordML folder.png

 

To use the Monitoring Tool:

1. Navigate to the Ephesoft application folder and open the log4j.xml file.

C:UsersEphesoftAppDataLocalMicrosoftWindowsINetCacheContent.Wordlog4j.png

2. Configure the Remote Log Appender:

  • Uncomment the section beginning with <Remote Name = Log Monitor> (lines 48-53 of the log4j.xml file)
  • Specify the TCP port which will be used by the tool
  • Specify the logs to be monitored

 

3. Navigate to the config folder of the Monitoring Tool and open the application.properties file (<Ephesoft Installation Directory>Applicationmonitoring-toolconfig).

C:UsersEphesoftAppDataLocalMicrosoftWindowsINetCacheContent.Wordconfig folder.png

4. Configure the Monitoring Tool by setting the appropriate properties. All properties are described in the table below.

C:UsersEphesoftAppDataLocalMicrosoftWindowsINetCacheContent.Wordconfig file.png

PropertySample ValueDescription
logging.filemonitor-log.logYou can remove this property if file logging is not required. If you want to keep the Monitoring Tool log, you can provide a name for the log file here.
logging.level.rootERRORLogging level of the root logger
logging.level.com.ephesoftDEBUGLogging level of the Monitoring Tool
spring.mail.hostsmtp.gmail.comEmail host from which alerts will be sent
spring.mail.port587Port number from which alerts will be sent
spring.mail.usernameabc@gmail.comEmail ID used for sending alerts
spring.mail.passwordxyz@32Password for the email ID used for sending alerts. The password can also be provided in encrypted form, see the Note below.
spring.mail.protocolsmtpEmail protocol
spring.mail.properties.mail.

smtp.starttls.enable

trueSet this property to True if you are using the STARTTLS protocol.

Set it to False if you are using another protocol

spring.thymeleaf.check-template-locationtrueIf this property is set to True, the system will check the location of the alert templates.

If this property is set to False, the system will not check the location of the alert templates.

Ephesoft recommends leaving this property unchanged.

spring.thymeleaf.templates-rootconfig/templatesBy default, email alert templates are located in the templates folder of the Monitoring Tool (<Ephesoft Installation Directory>Applicationmonitoring-toolconfigtemplates). You can provide your own path here for storing Monitoring Tool templates.
spring.thymeleaf.suffix.htmlSuffix that gets appended to view names when building a URL. Ephesoft recommends leaving this property unchanged.
alert.mail.to[0]

alert.mail.to[1]

Email ID to which alerts will be sent. You can add as many emails as required by copying and pasting the property and updating the number in the brackets.

* Please note there are no spaces when this property is modified even when its left blank else it gives error in running the start.bat.

alert.mail.fromEphesoft Support TeamThis is what will appear in the mail body as FROM. You can specify any sender name you require
alert.mail.subjectAlert!Subject of the alert email
alert.mail.template-file[0]

alert.mail.template-file[1]

alert.mail.template-file[2]

alert.mail.template-file[3]

alert.mail.template-file[4]

alert.mail.template-file[5]

alert.mail.template-file[6]

connectionError

connectionTimeout

logEventTimeout

logStorageAllocation

ioException

folderAllocation

diskAllocation

Names of the email templates. If you want to change this property, make sure to change the name of the template in the templates folder first (<Ephesoft Installation Directory>Applicationmonitoring-toolconfigtemplates) and only then update the name in the properties file.
log.monitor.log-event-switchON or OFFTurn this switch ON to start monitoring log events
log.monitor.log-allocation-switchON or OFFTurn this switch ON to start monitoring log size
log.monitor.hostnamelocalhostHostname of the server
log.monitor.port1234Port number used by the Monitoring Tool. This port should be the same as specified in the log4j.xml file.
log.monitor.date-formatyyyy-MM-dd HH:mm:ssDate pattern which will be used in alert emails containing a time stamp
log.monitor.storage.allocated-size200Size of the log in MB
log.monitor.storage.percentage75 (0 to 100)Percentage of log file size. When this threshold is reached or exceeded, the system administrator will receive an alert.
log.monitor.storage.reinitialize-on-connectfalseThis property governs whether to initialize the log file size to zero on application server reconnect. If set to False, it will start from the size which was captured before connection to the application server was lost.
log.monitor.event.connection-idle-timeout5Connection wait time (in minutes) after which the alert will be sent.
log.monitor.event.log-event-idle-timeout5Event wait time (in minutes) after which the alert will be sent.
file.monitor.disk-alert-switchON or OFFTurn this switch ON to start monitoring log folder disk size
file.monitor.file-alert-switchON or OFFTurn this switch ON to start monitoring log folder size
file.monitor.disk-percentage75 (0 to 100)Percentage of disk space. When this threshold is reached or exceeded, the system administrator will receive an alert.
file.monitor.log-folder-path../logsPath to the log folder
file.monitor.log-folder-percentage75 (0 to 100)Percentage of log folder size. When this threshold is reached or exceeded, the system administrator will receive an alert.
file.monitor.log-folder-allocated-size0.5Size of the log folder in MB

 

Note: Now, you can provide the email password in the encrypted form to ensure additional security of data. To do that:

  • Run the Encryptor utility (<Ephesoft Installation Directory>Application nativeencryptionEncryptor.bat)

C:UsersEphesoftAppDataLocalMicrosoftWindowsINetCacheContent.Word1.png

  • In the opened window, provide your password and click Enter. Then copy encrypted data.

C:UsersEphesoftAppDataLocalMicrosoftWindowsINetCacheContent.Word2.png

  • In the application.properties file, provide encrypted password under the spring.mail.password parameter according to the following pattern:

spring.mail.password=ENC(<encrypted_password>)

For example, spring.mail.password=ENC(LKSjKtRdBfETEoNnNQgi+fsn0s1X3Nu2).C:UsersEphesoftAppDataLocalMicrosoftWindowsINetCacheContent.Word3.png

 

5. Navigate to the monitoring-tool folder and double-click on the start file to start the tool (start.bat for Windows and start.sh for Linux).

C:UsersEphesoftAppDataLocalMicrosoftWindowsINetCacheContent.Wordml start.png

The tool is now monitoring logs according to the provided configuration and a log file is created in the Monitoring Tool folder.

C:UsersEphesoftAppDataLocalMicrosoftWindowsINetCacheContent.Wordml log.png

If the tool detects any event that requires the attention of the system administrator, it generates a log record and sends a real-time alert to all email accounts specified in the application.properties file of the Monitoring Tool:

C:UsersEphesoftAppDataLocalMicrosoftWindowsINetCacheContent.Wordemail alert1-1.png

C:UsersEphesoftAppDataLocalMicrosoftWindowsINetCacheContent.Wordemail alert2-1.png

Was this article helpful to you? Yes No