Infrastructure static endpoint will be deprovisioned on May 29th

What is being changed?
We are deprovisioning the current New Relic Infrastructure static ingest endpoint (https://static-infra-api.newrelic.com). The DNS entry for static-infra-api.newrelic.com will be updated to point to the same IP addresses the standard ingest service is using.

Why is this change happening?
The static ingest endpoint was made available for customers who restrict outbound network traffic because the default ingest endpoint (https://infra-api.newrelic.com) was originally hosted on a set of dynamic and unpredictable IP addresses. Since January, the default ingest endpoint has been running on a well-defined set of IP addresses and hence the static ingest endpoint is no longer needed.

Who will be affected?
Any customers who have set the collector_url property for their Infrastructure agents to https://static-infra-api.newrelic.com. Customers whose networks restrict outbound traffic and who have whitelisted the two existing static IP addresses (34.195.205.25:443 and 34.195.205.103:443) but not the standard New Relic IP ranges documented here will be unable to send Infrastructure data from agents in their network once the static ingest endpoint is decommissioned.

How can I check if I am affected by this change?
You will be affected if your network blocks outgoing traffic to our standard data ingest endpoints. If you haven’t set the agent’s collector URL to https://static-infra-api.newrelic.com and your agents are successfully reporting data, no action is needed. If you are using the static collector URL, you will be impacted if your network blocks traffic to the standard ingest location.

You can check whether any given host will be affected by attempting to access the following URL: https://infra-api.newrelic.com/metrics/events, from a host monitored by the Infrastructure agent:

  • If you receive no response or the request times out, that host will be unable to send its data once we make the change.
  • If you receive a message stating “Request is missing X-License-Key header” - this indicates a successful connection. (The error indicates that the request didn’t have a license key attached, but that’s expected. That message comes from our servers, which means the host was able to reach them, and that’s all we’re trying to check.)

When will this change take place?
The changes are scheduled to happen on May 29th.

What action do those affected need to take to prepare for this change?
Step 1: Ensure the firewall rules allow the following outgoing connections as explained in the documentation:

Networks:

  • 50.31.164.0/24
  • 162.247.240.0/22

Port:

  • TCP 443

Step 2: Remove the collector_url property from all the Infrastructure agent configuration files.

What will happen if I do NOT make this change?
After May 29th, agents which are blocked by your network from connecting to the above IP ranges will not report Infrastructure monitoring data, and the hosts will stop showing data in the Infrastructure UI. If you have configured Host Not Reporting alerts for these hosts, they will be triggered at that time as well. Hosts which are unable to send their data will not be counted for monthly compute unit usage while they’re disconnected.

A post was split to a new topic: Infrastructure agents not appearing