New Relic

Overview

The new Luciq integration with New Relic enables end-to-end tracing for network calls, connecting client-side and server-side monitoring for your network requests. By using a unique trace ID, you can follow any network request from the client to the server, providing insights for troubleshooting networking issues.

Prerequistes

New Relic

To use this integration, ensure the following prerequisites are met in your New Relic setup:

Distributed Tracing in Your Plan: Ensure that your New Relic plan includes distributed tracing.
New Agent Supporting W3C Context Propagation: You need to use a New Relic agent that supports W3C context propagation. More details can be found here.
Enable Distributed Tracing in Backend Agent: Distributed tracing must be enabled in your backend agent. More information is available here.

Note: if you use any trace sampling algorithms, New Relic may drop some traces. Consequently, you might see network requests in Luciq that are not available in New Relic.

Luciq

Supported Platforms: This integration is only supported for iOS and Android.
Luciq SDK Version: Ensure you have a minimum SDK v13.2.0 or higher on either iOS or Android.

Integration Steps

By setting up this integration, Luciq will attach a trace ID as an HTTP header to your network requests. This allows us to link network requests from Luciq to New Relic.

Go to Settings -> Integrations -> New Relic in your Luciq dashboard, and follow these integration steps:

Set Up

Enter your New Relic dashboard link. If you use custom domains for New Relic, replace one.newrelic.com with your company domain (e.g., x.newrelic.com). For redirecting to multiple organizations from the same app, use one.newrelic.com.

Test

Validate the New Relic dashboard link to ensure it is correct.

Finish

Ensure the APM - Network Requests checkbox is checked to trace network requests to New Relic, then give your integration a name and save the integration.