Introduction

New Relic is an application performance monitoring (APM) software that monitors the performance of web applications. Through its integration with New Relic, OverOps leverages its ability to capture data on why and how errors occur, by analyzing the application code at the environment level to enhance log data.

📘

Note

Currently supported only on the JVM languages listed here.

How Does It Work?

With the OverOps and New Relic integration, links are inserted directly into the log files so that deep, code-level context can be surfaced and accessed during the troubleshooting process using a single click.

These links are added in the following cases:

• An exception is thrown and is sampled by New Relic. This is true even if under its more strict security settings, the New Relic agent scrubs the exception tinylink from the exception message, in which case the OverOps Automated Root Case (ARC) screen will still be available.
• If you use the NewRelic.noticeError NR SDK API to explicitly send information about an error that wasn’t sampled by the New Relic agent. In this case, the integration instruments the New Relic agent and adds that information, which will then be show within the New Relic UI.

Integrating New Relic with OverOps

When OverOps and New Relic are installed on the same server, the integration will be activated automatically. Integration with New Relic works best when exception tiny links are enabled.

📘

Note

When attaching the OverOps Agent along with New Relic, we recommend that you put the OverOps Agent last in your list of environment arguments.

🚧

Important

New Relic is not currently supported on Java versions 10 and 11 and on the AIX Unix operating system.

Turning off the New Relic Integration

Use the following command in the Micro-Agent Properties to turn off the New Relic integration with OverOps:
-Dtakipi.no.newrelic.integration

Related Articles

Managing Alerts