Implementation with a Monitoring Platform for Observability with Elastic

Overview

Boomi AtomSphere

FileBeat and MetricsBeat Installation

The first step consist of installing the FileBeat and Metric Beat on each server. This step will link the server (or Cloud resource) to the ELK stack and will allows the gathering of logs, metrics, status of server, processes, network, etc.

APM Server Installation

The second step consist of installing the APM Server. This step will link the Java server to Elastic and will allows the connection of APM Client to the ELK Stack.

Java Agent Installation

The last step consist of installing the Java Agent on each Boomi runtime. This step will link the Java server to Elastic and will allows the gathering of JVM metrics and traces.

APM Setup

The Elastic Java Agent (Jar) needs to be deployed on each node or deployed on the Shared Server accessible by all nodes, once this is done Boomi System properties needs to be updated via Boomi AtomSphere:

Boomi AtomSphere

All the other configuration elements will be defined in elasticapm.properties (located in the same folder as the Java Agent Jar)

Example of elasticapm.properties

service_name=boomiatom
environment=development
...
secret_token=
server_urls=http://<APMServer>:8200

APM Configuration: Tracing and Custom Data Collector

Boomi JMS Processes

Boomi JMS processes do not require any change, they will be automatically detected by Elastic APM.

Boomi Scheduled Processes

The Boomi Scheduled processes won’tibe detected by Elastic APM and requires a manual instrumentation using Boomi APM Connector will minimize the changes:

Initial process:

APM Instrumented

The updated process will looks like the following:

APM Instrumented

The changes includes:

The APM Start shape at the beginning
The APM Stop shape before the last End, please note that we created a branch here as the Disk shape (Get) might not returned a Document thus an APM Stop shape after the Disk might not be called
The APM Error in the try catch

The Boomi APM Connector will allow the Instrumentation of any Boomi Processes and will provide with 3 steps: Start, Stop or Error

Boomi API Processes

In the context of Elastic APM, the Boomi API processes require manual instrumentation using the Boomi APM Connector. The changes required are the same as a Boomi Scheduled Process (see above).