Skip to main content

New Relic

Integrate New Relic Accounts with Cloudaware to inventory entities and link telemetry context to CMDB for unified reporting.

info
  • Audience: Cloudaware administrators, SRE teams, observability teams, and cloud operations teams
  • Outcome: The New Relic account is connected, the auto-collection of accounts is enabled, and New Relic objects are available in CMDB for reporting, coverage review, and asset correlation

Capabilities​

The integration supports:

  • Read-only discovery of New Relic accounts, entities, hosts, applications, synthetic monitors, and related resources
  • Relationship mappings between New Relic APM and infrastructure entities, Cloudaware Applications, and cloud assets in the CMDB
  • Search and reporting for New Relic objects using CMDB Navigator, CMDB list views, and reports

Prerequisites​

Before you begin, make sure you have:

  • Access to a Cloudaware account.
  • A user with access to the Admin Console and permissions to manage cloud accounts, organizations, and integrations (Cloudaware Administrator).
  • New Relic Account ID and Account Name.
  • Administrator permissions in New Relic to use API keys.
  • New Relic API Key with read permissions.
  • Optional: Query Key if your New Relic environment still uses it.

Add a New Relic Account to Cloudaware​

  1. In Cloudaware, go to Admin.
  2. Find New Relic Account, then click + ADD ACCOUNT.
  3. Enter the following values:
    • Account ID: Enter the New Relic account ID.
    • Account Name: Enter a display name for the New Relic account.
    • API Key: Click + ADD KEY and enter the New Relic API key.
      • Auto-Collects Accounts: Enable auto-collection if Cloudaware should collect New Relic data automatically.
    • Query Key (Deprecated): (optional) Click + ADD KEY and enter the Query Key (if required for your environment). Because the Insights Query API is no longer the preferred way to query New Relic data, it is marked as deprecated in Cloudaware.
  4. Click Save.
  5. Confirm that the integration status indicator is green.
tip

Allow the initial discovery cycle to complete after enabling the integration.

View New Relic Data in CMDB​

  1. In Cloudaware, open CMDB Navigator.
  2. In the left pane, select NEW RELIC.
  3. Open an object list, e.g., New Relic Hosts, to view records.

Supported Objects​

Cloudaware ingests the following New Relic objects:

New Relic ObjectCMDB Object API Name
New Relic AccountCA10N__CaNewRelicAccount__c
New Relic ApplicationCA10N__CaNewRelicApplication__c
New Relic Azure App ServiceCA10N__CaNewRelicAzureAppService__c
New Relic Azure Application GatewayCA10N__CaNewRelicAzureApplicationGateway__c
New Relic EntityCA10N__CaNewRelicEntity__c
New Relic HostCA10N__CaNewRelicHost__c
New Relic Host Application LinkCA10N__CaNewRelicHostApplicationLink__c
New Relic Linked Cloud AccountCA10N__CaNewRelicLinkedCloudAccount__c
New Relic Linked Cloud IntegrationCA10N__CaNewRelicLinkedCloudIntegration__c
New Relic Synthetic MonitorCA10N__CaNewRelicSyntheticMonitor__c
New Relic TransactionCA10N__CaNewRelicTransaction__c

Troubleshooting​

note

Initial data collection may take time to complete.

Authentication Fails or Integration Shows Red Status​

  • Verify that the Account ID and Account Name match the New Relic account.
  • Confirm that the API Key is valid, active, and has read permissions.
  • Check whether the Query Key is required for your New Relic environment and update it if needed.
  • Re-enter the credentials by editing the integration in Cloudaware.

New Relic Objects Are Missing​

  • Allow the initial discovery cycle to complete.
  • Confirm that the API Key has access to the missing New Relic entities, hosts, applications, or synthetic monitors.
  • Verify that auto-collection is enabled if Cloudaware should collect New Relic data automatically.
  • In CMDB Navigator, verify that you are viewing the NEW RELIC section and related resources.

Entity or Host Counts Do Not Match New Relic​

  • Confirm that you are comparing the same New Relic account and scope.
  • Review the permissions assigned to the API Key for entity and infrastructure access.
  • Wait for the next collection cycle if objects were recently added, removed, or updated in New Relic.

Still stuck? Contact Cloudaware Support at support@cloudaware.com with the integration name and a brief description of the issue.

Reconfigure or Remove the Integration​

warning

To rotate keys or update account settings, edit the existing integration instead of deleting and re-creating it.

Update the Integration Details​

  1. Go to Admin.
  2. Select New Relic.
  3. Select the specific integration.
  4. Open the three-dot menu (⋮), then click Edit.
  5. Update the required fields.
  6. Click Save.

Remove the Integration from Cloudaware​

  1. Go to Admin.
  2. Select New Relic.
  3. Select the specific integration.
  4. Open the three-dot menu (⋮), then click Delete.
  5. Confirm the deletion if prompted.

Security Notes​

  • Use a dedicated New Relic API key with the minimum read permissions required for Cloudaware discovery.
  • Avoid using personal administrator keys for long-running integrations.
  • Store New Relic API keys only in approved credential stores and avoid sharing them through tickets, chat, or documentation.
  • Rotate API keys according to your organization's credential-rotation policy and immediately after suspected exposure.
  • Remove unused Query Keys from the integration if they are no longer required by your New Relic environment.
  • Update the Cloudaware integration immediately if a key is revoked, regenerated, or replaced in New Relic.