Agent Environment

7.65.2 (now 7.64.1), helm 3.116.0 (Helm on AKS(k8s v1.32.3))

Describe what happened:

APM span and trace collection completely stopped after we enabled "Connect Logs and Traces" and "Data Streams Monitoring" via Remote Configuration. At that time, we saw a "500 Internal Server Error" related to remote config polling in the agent logs (log snippet provided below). We've since set those Remote Config features back to "Not Configured" and downgraded the Agent from 7.65.2 to 7.64.1 via Helm. The 500 error is gone, but APM data is still not being received. Log collection is working correctly.

[dd-remote-config] WARN datadog.remoteconfig.ConfigurationPoller - Failed to retrieve remote configuration: unexpected response code Internal Server Error 500 rpc error: code = Unknown desc = empty targets meta in director local store

Describe what you expected:

Container logs or APM metrics are still being collected successfully and can be found in Datadog. However, APM span or tracking data is still not being received. I want to tracking span/trace

Steps to reproduce the issue:

Agent (7.65.2) on AKS collecting logs/APM.
Enabled "Connect Logs and Traces", "Data Streams Monitoring" via Remote Config.
APM collection stopped immediately; 500 remote config error appeared.
Set Remote Config features back to "Not Configured".
APM Span/Trace not received.
Downgraded Agent to 7.64.1 via Helm.
Current state: Logs okay, APM Metric OK, Still APM Span/Trace not received.

I'm using an azure vnet, is there a domain other than '**.datadoghq.com ' that needs to open the firewall separately? Or a port other than 443?

And on the Datadog apm site it says Your current agent version is out of date (v6.34/v7.34 or older).