Skip to content

Latest commit

 

History

History
110 lines (64 loc) · 7.01 KB

README.md

File metadata and controls

110 lines (64 loc) · 7.01 KB

New Relic Open Source experimental project banner.

GitHub forks GitHub stars GitHub watchers

GitHub all releases GitHub release (latest by date) GitHub last commit GitHub Release Date

GitHub issues GitHub issues closed GitHub pull requests GitHub pull requests closed

New Relic Java Instrumentation for Boomi

Provides visibility into the Boomi Application

Installation

See Release Notes Below

Support

New Relic has open-sourced this project. This project is provided AS-IS WITHOUT WARRANTY OR DEDICATED SUPPORT. Issues and contributions should be reported to the project here on GitHub.

We encourage you to bring your experiences and questions to the Explorers Hub where our community members collaborate on solutions and new ideas.

Contributing

We encourage your contributions to improve [Project Name]! Keep in mind when you submit your pull request, you'll need to sign the CLA via the click-through using CLA-Assistant. You only have to sign the CLA one time per project. If you have any questions, or to execute our corporate CLA, required if your contribution is on behalf of a company, please drop us an email at opensource@newrelic.com.

A note about vulnerabilities

As noted in our security policy, New Relic is committed to the privacy and security of our customers and their data. We believe that providing coordinated disclosure by security researchers and engaging with the security community are important means to achieve our security goals.

If you believe you have found a security vulnerability in this project or any of New Relic's products or websites, we welcome and greatly appreciate you reporting it to New Relic through HackerOne.

License

[Project Name] is licensed under the Apache 2.0 License.

[If applicable: [Project Name] also uses source code from third-party libraries. You can find full details on which libraries are used and the terms under which they are licensed in the third-party notices document.]

Release Notes :

r1.0 : 04 APR 2023

This release carrying the instrumentation binaries for Boomi runtime

What are the components where new relic agent is required to be deployed

The 'Atom Node' JVM which handles the general management and housekeeping for the node. Not responsible for any actual data integration processing. This JVM does currently have a New Relic Agent associated with it. Currently the Atom Cloud telemetry data that is provided to the New Relic platform comes from the 'Atom Node' JVM. This is limited to higher level information about the Atom Cloud (e.g., number of processes running, number of attached sub-accounts, average execution time, queued executions, cluster issues). This is essentially the monitoring that our own Boomi operations team relies on with respect to the Boomi Public and Private Managed Atom Clouds. We monitor the cloud as a whole, versus drill down too far into individual processes and process connections.

The 'Atom Worker' JVMs which handle real-time, web service integration processes. These are spun up by the procworker.sh shell script and run for 24 hours. And then continually renewed for another 24 hours. Each Atom Worker JVM sits there and services multiple requests simultaneously (configurable). This is what SMEs are focused on. It looks very promising in terms of exposing telemetry data related to real-time processing. Including, potentially, the ability to 'see inside' the process. We have verified that Customers uses Atom Workers extensively. We counted as many as 26 Atom Workers attached to one of customer's production clouds. That cloud has 10 nodes. So it would be a matter of attaching a New Relic Agent to each Atom Worker instance.

So, 'Atom Node' and 'Atom Worker' where New Relic Agent needs to be deployed.

STEP1 : Deployment at 'Atom Node'

Apply Java agent and give App Name

Look for atom.vmoptions in your atom node installation and update javaagent [ The absolute path must point to your newrelic.jar within the agent installation location ] and app name with sudo privileges eg. /opt/Boomi_AtomSphere/Cloud/Cloud_atom_cloud_01/bin/atom.vmoptions and add the following options with pre-existing parameters

-Dnewrelic.config.app_name=BOOMI_EU_PROD_ATOM -javaagent:/home/ec2-user/nr_agent/newrelic/newrelic.jar

STEP 2: Deployment at 'Atom Worker'

Apply Java agent and give App Name

Look for procworker.sh in your atom node installation and carefully update javaagent and app name with sudo privileges eg. /opt/Boomi_AtomSphere/Cloud/Cloud_atom_cloud_01/bin/procworker.sh and add the following options with pre-existing parameters

-Dnewrelic.config.app_name=BOOMI_EU_PROD__WORKER -javaagent:/home/ec2-user/nr_agent/newrelic/newrelic.jar

STEP 3: Update the existing newrelic agent installation with following instrumented jars under extensions folder

Add the following jar files from Release bundle

Create extensions folder [ if the folder doesn't exist]

 E.g. /home/ec2-user/nr_agent/newrelic/extensions

boomi-container-execution.jar

kafka-clients.jar

executors-10.jar

executors-17.jar

rmi-stubs.jar

rmi.jar

executors-8.jar

smallrye-mutiny.jar

executors-9.jar

STEP 4: Restart all the nodes

STEP 5: Verify the New Relic Platform and check for both ATOM and Worker applications