New Relic

A New Relic integration can be added by providing Grepr with a license key (opens in a new tab) via either the UI or the API. The license key is used to send logs to your New Relic account. You should use the same License key in your agent as the one you configure in Grepr.

Server logs

To send data to Grepr, you configure the agents to send logs to Grepr instead of New Relic. This involves changing the logging endpoint in the tool being used to forward logs to New Relic.

The endpoint that you need to configure has the following format: https://<integration-id>-<org-id>.ingest.grepr.ai/nr/log/v1. The Grepr UI makes it available for copying in the Sources section of the pipeline details page. Otherwise, the integration-id is the ID of the New Relic integration that you'd like to use, available via the API. Ingest URL

Creating a New Relic Integration in Grepr

To create a New Relic integration, follow the instructions below.

Go to the Integrations page in the Grepr UI and click on the Add new button in front of Observability Vendors.
Select New Relic from the list of vendors.
Enter a name for the integration
Enter the license key that agents are using to forward logs to New Relic.

Fluent Bit plugin

If you are using the Fluent Bit plugin (opens in a new tab) for log forwarding, update the fluent-bit.conf to forward logs to Grepr.

...
[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 to the fluent-bit.conf file:

# Send all logs to New Relic directly
[OUTPUT]
    Name       newrelic
    Match      *
    licenseKey YOUR_LICENSE_KEY

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

Fluent-d plugin

If you are using the Fluentd plugin (opens in a new tab) for log forwarding, update the fluent.conf to forward logs to the Grepr

#Forward all events to New Relic
<match>
  @type newrelic
  license_key YOUR_LICENSE_KEY
  # This is the only configuration change needed to send logs to Grepr
  base_uri https://<integration-id>-<org-id>.ingest.grepr.ai/nr/log/v1
</match>

To dual ship logs, use the copy output plugin (opens in a new tab)

<match>
  @type copy
  <store>
    @type newrelic
    license_key YOUR_LICENSE_KEY
    base_uri https://<integration-id>-<org-id>.ingest.grepr.ai/nr/log/v1
  </store>
  <store>
    @type newrelic
    license_key YOUR_LICENSE_KEY
  </store>
</match>

Kubernetes plugin

If you are using the Kubernetes plugin (opens in a new tab) for forwarding logs, you can update the newrelic-logging section of the values.yaml to forward logs to the Grepr.

  enabled: true
  # If endpoint is configured, change it here as well
  # endpoint: https://<integration-id>-<org-id>.ingest.grepr.ai/nr/log/v1
  fluentBit:
    config:
      # ...
      outputs: |
        [OUTPUT]
            Name           newrelic
            Match          *
            licenseKey     ${LICENSE_KEY}
            endpoint       https://<integration-id>-<org-id>.ingest.grepr.ai/nr/log/v1