DevOps Guide


The only 3rd party product used by GLU are 

– Java Version 1.8 

– A server to host the Java virtual machine (Docker/VM/server)

The GLU.Engine Server hosts the executable generated by the GLU.Console to provide integration. It takes the form of a .JAR file (i.e. Springboot Container). Each ‘Application’ equates to one GLU.Engine and each GLU.Engine can be deployed on its own Hardware as outlined below and depending on port values. 

This Hardware recommendation is provided as a baseline specification to be considered in parallel with the performance expectations. 

If there is an expectation of high or system performance, CPU & memory should be increased. 

To provide scale a GLU.engines can be scaled horizontally utilising a load balancer as part of the solution or a GLU.Engine setup as a Decision Maker to send transactions to a set of GLU.Engines running parallel. Please contact GLU support for more details on setting up these architectures. 

Server Specifications

GLU.Engine Server Specifications

GLU Engine Deployment Guidelines

GLU.Engine Deployment Guidelines

Monitoring Deployment Guidelines

GLU.Monitoring Deployment Guidelines

Logging Deployment Guidelines

GLU.Logging Deployment Guidelines

Engine APIs

GLU.Analytics or GLU.Engine APIS. Set of APIs exposed through the server port to provide data on the running GLU.Engine.

GLU.Engine APIs

Swagger web page

The swagger web page will be accessible through a web page on the following URL 

http://{URL for the GLU.Engine}:{serverPort}/swagger

For more information on understanding the swagger page please refer to Generate OpenAPI 3.0 (Swagger)

Deploying and running a GLU.Engine

A GLU.Engine can be deploy in the following ways 

  • A GLU.Engine deployed on a server.
  • A GLU.Engine deployed in docker container manager such as SwarmPit, Kubernetes docker desktop.

The diagram below describes how the GLU.Engines can be set up with 3rd party monitoring and logging analytic capabilities as well as an internal web page generated to show swagger definition for the APIs in the GLU.Engine. 


GLU recommends the use of Grafana on a separate server to monitor and provide alerts on data coming from the data produced by the GLU.Engine. 

Prometheus and node exporter can be used on the GLU.Engine server to gather and send the monitoring data to Grafana. 

For Logging GLU recommends Elastic Search and provides a configuration of filebeats to facilitate either pushing the GLU.Engine logs to ElasticSearch or to Logstash. 

Direct to ElasticSearch

Setup approach for logging where logs sent direct to ElasticSearch.


Setup approach for logging where logs sent direct to Logstash.

Was this article helpful?

Related Articles

Leave a Reply

Your email address will not be published. Required fields are marked *

Fill the form and we’ll contact you shortly

    I agree with

    We uses cookies to make your experience on this website better. Learn more
    Accept cookies