Issue: Network attacks default to excluding api.gremlin.com hostname so as to not impact communication with the Gremlin Control Plane when running the attack. This causes a problem when a proxy is configured with Gremlin agent and the DNS server is not aware of api.gremlin.com.A part of the setup of the attack is to make a DNS call to resolve api.gremlin.com in order to exclude it which results in this type of error in the logs:
error trying to connect: dns error: no record found for name: api.gremlin.com……
Remediation: Remove the ^api.gremlin.com exclusion from network attacks in the UI/API and rerun the attack. The agent will continue to report the clients as Unhealthy since the agent still runs the latency validation attacks on startup with the api.gremlin.com hostname. You can ignore the warnings on the attack page or upgrade the agent to the one that will have the fix for this proxy issue.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article