Skip to content

Getting the FusionReactor agent

So the first thing we are going to cover is how to get the installation files needed for the beta, to do this you need the beta FusionReactor agent.

When you next log into FusionReactor Cloud, you will see the new logging features have been made available. You now have the ability to ship and explore your logs including the ability to create insightful dashboards from your log data, but first you need to send us some logs.

Quick steps

  1. Download the FusionReactor beta agent
  2. Replace your existing fusionreactor.jar file with the beta agent
  3. Restart or Redeploy your application server

How to download the agent

You can download the FusionReactor agent with logging capabilities using the S3 download link.

For the beta we are not releasing an installer build, so updates will have to be performed using the manual installation method. Upon official release we will then package the jar into an installer.

There is no requirement to update the debug library for this beta build, provided you are already running an 8.7.x debug library in your install. If you are running an older agent (pre 8.7.x), you should retrieve the latest release debug library which you can find the link for within the documentation.

How to deploy the agent

Now you have downloaded your beta FusionReactor agent, it is time to install and run this version.

You may already have a scripted update process in place, in which case you can follow that process with the new jar file. If that is not the case, below is how to update in a few different scenarios.

In a hosted server based configuration

In a server based install, we want to follow the manual installation upgrade guide.

To do this follow these steps:

  1. Stop your Application Server
  2. Download the latest FusionReactor installation files
  3. Replace the FusionReactor installation files for each instance
  4. Start your Application Server

See the documentation above for more detailed information on doing this.

In a container environment

In a container such as K8, Docker or similar environments you will need to update the url or file you are using within your running containers.

An example of this would be: ADD https://intergral-download.s3.eu-west-1.amazonaws.com/FR/BetaLogs/fusionreactor.jar /opt/fusionreactor/instance/tomcat/fusionreactor.jar

Depending on how you have setup your container deploy, you may need to rebuild your container image with the new FusionReactor version.

Using an environment variable for the download URL of FusionReactor and fetching the jar as part of a container deploy is a good way of avoiding this.

In CommandBox

With CommandBox you will need to uninstall the CommandBox module and manually add jvm arguments to your box installation.

An example of this would be:

    box uninstall commandbox-fusionreactor --system
    wget https://intergral-download.s3.eu-west-1.amazonaws.com/FR/BetaLogs/fusionreactor.jar -0 {path}/fusionreactor.jar
    wget https://download.fusionreactor.io/FR/Latest/libfrjvmti_x64.so -0 {path}/libfrjvmti_x64.so
    box server set JVM.args="-javaagent:{path}/fusionreactor=name={name},address={port} -agentpath:{path}/libfrjvmti_x64.so -Dfrlicense={license_key}"