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 API specification.

Although this page describes using an integration to create a pipeline for sourcing and sending data with a single observability platform, your pipelines can use multiple integrations to source and sink data for different platforms. For example, you can create a pipeline with a Datadog integration that’s used to source data from Datadog agents, and a Splunk integration and sink that sends the pipeline output to Splunk.

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. The user key must match the one the New Relic collectors use.

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:

Go to the Integrations page in the Grepr UI and click Add new next to Observability Vendors.
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) Select a time window to specify how far back Grepr should look for dashboards and alerts when performing automatic exception parsing.
Click Create.

Step 2: Add a source to your pipeline

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

In the Grepr UI, go to the overview page for an existing pipeline or create a new pipeline from the homepage.
In the left-hand navigation menu on the pipeline overview page, click Sources.
In the Add source dialog, select the New Relic integration in the Source menu.
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.

Accessing the Grepr ingestion URL in the UI.

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

https://<integration-id>-<org-id>.ingest.grepr.ai

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:

Fluent Bit

To configure Fluent Bit to forward logs to Grepr, update the configuration in fluent-bit.conf by setting the endpoint value in the [OUTPUT] section to the ingestion URL from your Grepr source:


[OUTPUT]
    Name       newrelic
    Match      *
    licenseKey YOUR_LICENSE_KEY
    # This is the only configuration change needed to send logs to Grepr
    endpoint   https://<integration-id>-<org-id>.ingest.grepr.ai/nr/log/v1

Fluent bit can also be configured to dual-ship logs to New Relic and Grepr. To do this, add another [OUTPUT] section to the fluent-bit.conf file for New Relic:


# Send logs to New Relic directly
[OUTPUT]
    Name       newrelic
    Match      *
    licenseKey YOUR_LICENSE_KEY
 
# Send logs to Grepr
[OUTPUT]
    Name       newrelic
    Match      *
    licenseKey YOUR_LICENSE_KEY
    endpoint   https://<integration-id>-<org-id>.ingest.grepr.ai/nr/log/v1