DX OI SaaS - issues with getting data into the OI platform when using RESTmon 2.2 settings with New Relic

Products

• DX Operational Intelligence

Issue/Introduction

You can have some issues with getting data into the OI platform when using RESTmon 2.2 settings with New Relic. You may receive data from New Relic, but it is not populating. 

Environment

DX Operational Intelligence  21.3.1 
RESTmon 2.2

Cause

The authentication used in basic RESTmon file was inappropriate for New Relic. 

Resolution

Please update the profile in restmon.json to use "none" authentication as below and check again.

 

"restapiconnectdetails": {

    "type": "https",

    "hostname": "insights-api.newrelic.com",

    "port": "443",

    "authentication": "none",

    "username": "",

    "password": "",

    "realmdomain": "",

    "token": "<token>",

    "httptimeout": "120000",

    "checkcert": "no",

    "accountId": "1718962"

}

Also please update the "API-Key" value appropriately in the schema definition headers if not done already.

Additional Information

We recently tested the New Relic schema with RESTmon 2.2 with New Relic on SaaS

This is New Relic Profile from the RESTmon.json

{
      "profile" : {
        "name" : "newrelic",
        "active" : "no",
        "schema" : "newrelic",
        "polling_interval_secs" : "300",
        "alarms_polling_interval_secs" : "15",
        "metrics_polling_interval_secs" : "60",
        "topology_polling_interval_secs" : "900",
        "inventory_topology_fullsync_interval_mins" : "30",
        "topology_ttl_mins" : "60"
      },
      "restapiconnectdetails" : {
        "type" : "https",
        "hostname" : "insights-api.newrelic.com",
        "port" : "443",
        "authentication" : "none",
        "username" : "",
        "password" : "",
        "realmdomain" : "",
        "token" : "w4Hu02F81v7WNXQm+JmRkWwJBv0kaYToanoXfNDmqfizTN8G/24t4TunPaqrQWpD",
        "httptimeout" : "120000",
        "checkcert" : "no",
        "accountId" : "3445424"
      },
      "monitored_groups" : {
        "Topology" : "yes",
        "Alerts" : "yes",
        "ApplicationAgentCheck" : "no",
        "ApplicationAjax" : "no",
        "ApplicationApex" : "no",
        "ApplicationApmSummary" : "yes",
        "ApplicationBjax" : "no",
        "ApplicationBrowser" : "no",
        "ApplicationBrowserSummary" : "no",
        "ApplicationCPU" : "no",
        "ApplicationDatastore" : "no",
        "ApplicationEndUser" : "no",
        "ApplicationError" : "no",
        "ApplicationErrors" : "no",
        "ApplicationExternal" : "no",
        "ApplicationGC" : "no",
        "ApplicationInstance" : "no",
        "ApplicationJava" : "no",
        "ApplicationJMXBuiltIn" : "no",
        "ApplicationMemory" : "no",
        "ApplicationMemoryPool" : "no",
        "ApplicationNetwork" : "no",
        "ApplicationOtherTransaction" : "no",
        "ApplicationSupportability" : "no",
        "ApplicationThreads" : "no",
        "ApplicationTransaction" : "no",
        "ApplicationWebFrontendErrors" : "no",
        "InfraCPU" : "no",
        "InfraDisk" : "no",
        "InfraHostSummary" : "yes",
        "InfraMemory" : "no",
        "InfraNetwork" : "no",
        "InfraProcess" : "no",
        "InfraSwap" : "no"
      }
    }

This is a snippet from the New Relic schema, notice X-Api-Key is pulled from the token key in RESTmon.json and the API-key is hardcoded in the schema. These keys are from our test New Relic SaaS instance, so please do not use them.

The API-key comes from 

Administration - API Keys

X-api-key (restmon.json token) comes from

This key comes from here https://rpm.newrelic.com/accounts/3445424/integrations?page=api_keys

"definition": {
      "resource_category": null,
      "uploadedBy": "RESTmon",
      "updatedBy": "",
      "version": "2.0",
      "defaults": {
        "checkcert": "no",
        "port": 443,
        "interval": 60,
        "httptimeout": 30000,
        "headers": {
          "X-Api-Key": "%token",
          "API-Key": "NRAK-NZZE86FDWBD084XHJN3R3R4F30O"
        }
      },
      "auth": "none",
      "xml_ns": "",
      "name": "newrelic",
      "type": "https"
    },

The following documentation can be also useful when configuring New Relic integration in general:

Configure RESTMon for the New Relic Environment
https://techdocs.broadcom.com/us/en/ca-enterprise-software/it-operations-management/dx-operational-intelligence-saas/SaaS/Integration/DX-OI-Inbound-Integration/DX-OI-Third-Party-Integration/Monitor-Using-DX-RESTmon/Monitor-Data-Using-DX-RESTmon/DX-RESTmon-Connectors/New-Relic.html