GLU.Engine Logging Approach

Each GLU.Engine has within it a number of classes. For example a dedicated class is responsible for Orchestration Handlers and other classes would be responsible for Protocol specific connectors. As from GLU.Ware release v1.9.17 each class within a GLU.Engine takes care of the overhead of printing its own logs to the gluware.log file. Additionally the process of printing of log entries is now asynchronous. These two changes bring a material performance improvement to your GLU.Engines as well as allowing for finer control of logging for each area of the GLU.Engine execution.


For more information on how to utilise the logging levels broken up into classes please contact GLU Support.

GLU.Engine Server Specification

16 GB RAM 

100 GB SSD disk (or high speed 15k RPM drives) 

1 Dual Core CPU (x86_64)

Operating System: Ubuntu (latest version 18.04 or later)

Java Virtual Machine (JVM) – Java 8

GLU.Engine Prerequisites

Java installed – version 1.8 of java

$ java -version
openjdk version "1.8.0_201"
OpenJDK Runtime Environment (build 1.8.0_201-b09)
OpenJDK 64-Bit Server VM (build 25.201-b09, mixed mode)

If Java needs to be installed use this command (assuming yum is supported with the OS.)

$ yum install java-1.8.0-openjdk.x86_64

Optional Elastic Stack Deployment

Separate servers are needed to run the Elastic systems. 

For testing purposes just a single server can be used.

For Production an analysis of the the following metrics (sometimes called load testing or performance testing) needs to be conducted in order to ascertain the sizing of the Server/s. 

• forecast transaction volumes
• log levels and types
• retention periods
• system availability requirements
• transaction protocols being used, see list Connectors 
• number of expected inflight transactions, see Throttle Type 2: Concurrent Requests using Thread Pools 
• number for the Max Connections, see Max Connections 
  
  

Depending on client configuration choices, the three components of the Elastic Stack are 

• ElasticSearch
• Logstash
• Kibana
  
  

(plus filebeats which is deployed on the server the GLU.Engine is running to gather and deliver the logs to either Logstash or ElasticSearch depending on the configuration.)

Optional Network Prerequisites for Elastic Stack

Quick reference to the ports which need to be opened against each of the Elastic components.Port Server ELK serverice Area

Optional Install Instructions links for Elastic Stack

Please refer to the Elastic stack documentation for install instructions.

ElasticStackInstallGuide

GLU.Engine logs have been tested with the following versions of Elastic Stack

Kibana 7.8 [1]

Elasticsearch 7.8 [2]

–> Separate server is direct files to be sent to Logstash 

Logstash 7.8 [3]

–> deployed on GLU.Engine Server (details of filebeats configuration file)

filebeats 7.8 [4]