Skip to main content

Destination

Nexla's bi-directional connectors allow data to flow both to and from any location, making it simple to create a FlexFlow, DB-CDC, Spark ETL, or Replication data flow that sends data to a New Relic location.
newrelic_api.png

New Relic

Create a New Relic Destination​

  1. Click the + icon on the Nexset that will be sent to the New Relic destination, and select the Send to Destination option from the menu.

  2. Select the New Relic connector from the list of available destination connectors. Then, select the credential that will be used to connect to your New Relic account, and click Next; or, create a new New Relic credential for use in this flow.

  3. In Nexla, New Relic destinations can be created using pre-built endpoint templates, which expedite destination setup for common New Relic endpoints. Each template is designed specifically for the corresponding New Relic endpoint, making destination configuration easy and efficient.
    • To configure this destination using a template, follow the instructions in Configure Using a Template.

    New Relic destinations can also be configured manually, allowing you to send data to New Relic endpoints not included in the pre-built templates or apply further customizations to exactly suit your needs.
    • To configure this destination manually, follow the instructions in Configure Manually.

Configure Using a Template​

Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common New Relic endpoints. Each template is designed specifically for the corresponding New Relic endpoint, making destination setup easy and efficient.

  • To configure this destination using a template, select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.

    Add browser apps

    This endpoint template creates new browser applications in your New Relic account. Use this template when you need to add browser monitoring applications to track web application performance and user experience metrics.

    • This endpoint automatically creates browser applications from your data. No additional configuration is required beyond selecting this endpoint template. The request body should contain the browser application data in JSON format.

    This endpoint sends data as JSON in the request body to create new browser applications in your New Relic account. The request body should contain the browser application configuration data, including application name, settings, and other configuration options.

    For detailed information about creating browser applications, request body formats, and available configuration options, see the New Relic REST API documentation.

    Generate infrastructure condition

    This endpoint template creates new infrastructure alert conditions in your New Relic account. Use this template when you need to set up infrastructure monitoring conditions to track system health and trigger alerts based on infrastructure metrics.

    • This endpoint automatically creates infrastructure conditions from your data. No additional configuration is required beyond selecting this endpoint template. The request body should contain the infrastructure condition data in JSON format.

    This endpoint sends data as JSON in the request body to create new infrastructure alert conditions in your New Relic account. The request body should contain the infrastructure condition configuration data, including condition name, thresholds, and alert settings.

    For detailed information about creating infrastructure conditions, request body formats, and available configuration options, see the New Relic Infrastructure API documentation.

Configure Manually​

New Relic destinations can be manually configured to send data to any valid New Relic API endpoint. Manual configuration provides maximum flexibility for accessing endpoints not covered by pre-built templates or when you need custom API configurations.

Using manual configuration, you can also configure Nexla to automatically send the response received from the New Relic API after each call to a new Nexla webhook data source.

API Method​

  1. To manually configure this destination, select the Advanced tab at the top of the configuration screen.

  2. Select the API method that will be used for calls to the New Relic API from the Method pulldown menu. New Relic API typically uses POST method for creating resources.

Data Format​

  1. Select the format in which the Nexset data will be sent to the New Relic API from the Content Format pulldown menu. New Relic API expects JSON format for all requests.

API Endpoint URL​

  1. Enter the URL of the New Relic API endpoint to which data will be sent in the URL field. This should be the complete URL including your root URL (from your credential), the API path (e.g., /browser_applications.json), and any required query parameters (e.g., https://api.newrelic.com/v2/browser_applications.json). Include any required query parameters in the URL.

Ensure the API endpoint URL is correct and accessible with your current credentials. The New Relic API endpoint URL should point to the endpoint where you want to create resources. You can test the endpoint using the Test button after configuring the URL.

Request Body​

  1. Configure the request body that will be sent to the New Relic API. The request body should contain the resource data formatted as JSON. The request body format is typically {message.json} to send the entire Nexset data as JSON, or you can construct a custom JSON structure with specific field mappings.

The request body must be valid JSON and must match the New Relic API's expected format for the specific endpoint you're using. For detailed information about request body formats, available endpoints, and configuration options, see the New Relic REST API documentation.

Save the Destination​

  1. Once all of the relevant steps in the above sections have been completed, click the Next button to proceed with the rest of the data flow configuration, or click Save to save the destination configuration for later use.