New Relic APM telemetry gap after collector connectivity loss

A New Relic APM agent stops sending metric, event, trace, and log data when it cannot reach its configured regional collector endpoint. Connectivity loss may result from an incorrect region URL, outbound firewall rules blocking port 443, or an invalid license key.

The goal is to determine whether delivery resumes automatically after connectivity is restored, and how long previously reported entity names and tags remain visible after a service is renamed or decommissioned.

Behavior varies by language agent version and region. Older agents may not honor newer endpoint URLs or may retry differently after connection failure. Local spooling differs by agent, and unsent data may not survive a restart. Whether renaming a service merges history or creates a new entity is not consistently documented.

• Does the agent resume harvest cycles automatically after transient collector connectivity is restored?
• What retention period does New Relic apply to stale entity metadata before garbage collection?
• Does renaming a service preserve existing history under the same GUID or create a new entity?