What criteria does the platform use when matching New Relic hosts to instances?
search cancel

What criteria does the platform use when matching New Relic hosts to instances?

book

Article ID: 283205

calendar_today

Updated On:

Products

CloudHealth

Issue/Introduction

Matching New Relic hosts is complicated because typically, no other metadata associated with a New Relic server exists. The primary assumption during the matching process is that only the server name is available for matching.

Nevertheless, the platform attempts matching based on the following attributes. The attributes are matched in this sequence.

  1. EC2 Instance ID
  2. EC2 Private IP
  3. EC2 Instance Name
  4. Instance ID embedded in server name (not an exact match): regex /(i-\w{17}|i-\w{8})/
  5. Private IP embedded in server name (not an exact match): regex /(\d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3})/
  6. Public IP embedded in server name (same regex)
  7. Partial instance ID with the 'i-' stripped off embedded in the server name
  8. Partial matching using the first part of a dot delimited server name, for example, api-lb1.va.example.net -> api-lb1