New Relic Update

Update the Installed New Relic Monitoring Add-On

The New Relic add-on includes a built-in update option that checks the relevant repositories for newly released agent versions and installs available updates without requiring a manual agent-upgrade process.
On this page

Check for Agent Updates

1Open the Add-Ons panel

Locate the application-server node where New Relic is installed and click Add-Ons.

2Select Update Agent

Find the installed New Relic add-on, click the gear icon in its upper corner, and choose Update Agent.

Update New Relic agent from the Add-Ons panel
Open the New Relic add-on menu and select Update Agent.

3Confirm the update check

In the confirmation window, click Yes to check whether a newer agent version is available.

Confirm New Relic update check
Confirm the request to check for New Relic agent updates.

Download and Install the Update

The platform checks the corresponding repository for a newer New Relic agent version. When update files are available, they are downloaded and installed automatically.

New Relic update in progress
The platform downloads and installs the available New Relic update.
When no newer version is available, the installed agent remains unchanged.

Restart the Application Server

After the add-on is updated successfully, a notification appears in the upper-right corner of the dashboard and recommends restarting the application-server instance so the new agent files can be loaded.

Restart application nodes after New Relic update
Restart the application-server node after the update is completed.

4Restart the node

Click the restart control beside the application-server node and wait until the server returns to the running state.

Downtime Considerations

Single Application Server Restarting the only application-server node causes temporary application downtime. Perform the restart during a suitable maintenance period.
Horizontally Scaled Layer The platform can restart instances sequentially so that other nodes remain active while one node is under maintenance.
Minimise interruption: Configure a delay between sequential node restarts so each updated server has time to become ready before the next node is restarted.

Check the Installed Agent Version

  • Java application servers: Review the logs/newrelic_agent.log file inside the directory containing the New Relic add-on files.
  • PHP application servers: Check the New Relic information in the phpinfo() output.
The exact Java add-on directory depends on the application-server type and follows the installation paths documented for the New Relic agent.

After the restart, the updated New Relic agent is ready to collect application-performance information using the newer available functionality.

What’s next?