Configure New Relic connections for integration with Grepr

The New Relic integration enables you to ingest logs into Grepr with a Grepr source, process them with a Grepr pipeline, and then send the processed logs to New Relic with a Grepr sink.

To send logs to a Grepr pipeline before forwarding the logs to New Relic, you change your collector configuration to send the logs to a Grepr endpoint URL instead of a New Relic endpoint. The Grepr New Relic integration supports the Fluent Bit and Fluentd collectors.

You can use the Grepr UI or REST API to add a New Relic integration. To learn how to create a New Relic integration in the Grepr UI and configure collectors to send logs to Grepr, see Use a New Relic integration in a Grepr pipeline.

To use the REST API, see the New Relic Integration specification.

Requirements

• To create a New Relic integration, you must have a license key from your New Relic account. Use the same license key as the collectors that forward logs to New Relic. This key is required to authenticate the connection between Grepr and New Relic.
• (Optional) To enable Grepr’s automatic exception parsing feature, you must have the Account ID and a user key from your New Relic account. See Enable selective reduction with a New Relic integration. The user key must match the one the New Relic collectors use.

Enable selective reduction with a New Relic integration

When you include a New Relic user key and account ID in your integration configuration, Grepr automatically tracks dashboards and alerts configured in your New Relic account. By parsing queries used in these dashboards and alerts and making them available as exceptions to the Log Reducer, Grepr can determine which messages should not be processed.

To see a full list of exceptions from the parsed alerts and dashboards, in the Observability vendors section of the Integrations page in the Grepr UI, click on the cloud sync icon under Actions.

To learn more about Grepr log reduction, see Optimizing logs with Grepr’s intelligent aggregation.

Use a New Relic integration in a Grepr pipeline

Use the following steps to create a New Relic integration in the Grepr UI and use it in a pipeline to source and sink data.

Step 1: Create a New Relic integration

To create a New Relic integration in the Grepr UI:

1. Go to the Integrations page in the Grepr UI and click Add new next to Observability Vendors.

   

2. In the Add Observability Vendor dialog:

   • In the Type menu, select New Relic.
   • In the Name field, enter a name for the integration.
   • In the License Key field, enter the license key from your New Relic account. Use the same license key as the collectors that forward logs to New Relic. Do not enter a user key in this field.
   • (Optional) Enter the Account ID for your New Relic account. This value is only required if you choose to enable Grepr’s automatic exception parsing feature.
   • (Optional) In the User Key field, enter a New Relic user key. Use the same user key that the New Relic collectors use. This value is only required if you choose to enable Grepr’s automatic exception parsing feature.
   • (Optional) Specify how recently a dashboard must have been accessed to be included in automatic exception parsing. By default, Grepr checks for activity within the last 28 days.

3. Click Create.

Step 2: Add a source to your pipeline

To add a source to your pipeline that uses the New Relic integration:

1. In the Grepr UI, go to the overview page for an existing pipeline or create a new pipeline from the homepage.
2. In the left-hand navigation menu on the pipeline overview page, click Sources.
3. In the Add source dialog, select the New Relic integration in the Source menu.
4. Click Submit.

Step 3: Configure log forwarding to Grepr

To send data to Grepr, you configure your collector or agent to send the data to the ingestion URL for your Grepr integration, rather than sending it to your observability vendor’s platform. To find the ingestion URL when using the Grepr UI to configure your pipeline, go to the details view for the pipeline, click Sources in the left pane, and copy the Ingest URL.

When you use the API, you can construct the ingestion URL using the following format:

Replace <integration-id> with the identifier of the vendor integration used by your pipeline and replace <org-id> with the identifier for your organization.

To see more information and configuration examples, select the tab for your preferred log collector:

[OUTPUT]
    Name       newrelic
    Match      *
    licenseKey <nr-license-key>
    endpoint   <ingestion-url>

# Send logs to New Relic directly
[OUTPUT]
    Name       newrelic
    Match      *
    licenseKey <nr-license-key>
 
# Send logs to Grepr
[OUTPUT]
    Name       newrelic
    Match      *
    licenseKey <nr-license-key>
    endpoint   <ingestion-url>

<match your_tag.**> # Adjust your match pattern as needed
  @type newrelic
  license_key <nr-license-key>
  base_uri <ingestion-url>
</match>

<match your_tag.**>
  @type copy
  <store>
    @type newrelic
    license_key <nr-license-key>
    base_uri <ingestion-url>
  </store>
  <store>
    @type newrelic
    license_key <nr-license-key>
  </store>
</match>

Limitations

• The New Relic integration supports only HTTP/HTTPS connections. TCP connections are not supported.