New Relic Ingest

​

🚀 Quickstart

curl -X POST "https://api.nango.dev/proxy/metric/v1" \
  -H "Authorization: Bearer <NANGO-API-KEY>" \
  -H "Provider-Config-Key: <INTEGRATION-ID>" \
  -H "Connection-Id: <CONNECTION-ID>" \
  -H "Content-Type: application/json" \
  -d '[{"metrics":[{"name":"nango.test","type":"gauge","value":1,"timestamp":'"$(date +%s)"',"attributes":{"host.name":"nango-quickstart"}}]}]'

import { Nango } from '@nangohq/node';

const nango = new Nango({ apiKey: '<NANGO-API-KEY>' });

const res = await nango.post({
    endpoint: '/metric/v1',
    data: [
        {
            metrics: [
                {
                    name: 'nango.test',
                    type: 'gauge',
                    value: 1,
                    timestamp: Math.floor(Date.now() / 1000),
                    attributes: { 'host.name': 'nango-quickstart' }
                }
            ]
        }
    ],
    providerConfigKey: '<INTEGRATION-ID>',
    connectionId: '<CONNECTION-ID>'
});

console.log(res.data);

​

📚 New Relic Ingest integration guides

• How do I link my account?
  Find your data center region and create a license key to connect your New Relic account.

​

🧩 Pre-built syncs & actions for New Relic Ingest

​

API gotchas

• The Event API is served from insights-collector.newrelic.com (US), insights-collector.eu01.nr-data.net (EU) or insights-collector.jp.nr-data.net (JP), not from the connection’s Metric API host. Call it with baseUrlOverride set to the host for the connection’s region; Nango keeps the connection’s credentials and headers. See Send custom events with our Event API.
• The Log API is served from log-api.newrelic.com (US), log-api.eu.newrelic.com (EU) or log-api.jp.nr-data.net (JP). Call it with baseUrlOverride set to the host for the connection’s region; Nango keeps the connection’s credentials and headers. See Send your logging data with our Log API.
• The Trace API is served from trace-api.newrelic.com (US), trace-api.eu.newrelic.com (EU) or trace-api.jp.nr-data.net (JP). Call it with baseUrlOverride set to the host for the connection’s region; Nango keeps the connection’s credentials and headers. See Choose your data center.
• Nango does not check the key when a connection is created, so a wrong or revoked key still connects and fails on its first call.
• To query data or manage configuration through NerdGraph, use the new-relic integration, which connects with a User key.