Before installing the Gremlin Agent, be sure to review the following prerequisites:
To help identify a Service's fingerprint, you will need to use tags (such as operating system, zone, or local-hostname). Cloud providers generally have default tags but if you are not using a cloud provider, you will need to create custom tags in your environment and assign them to the Gremlin Agent during installation. See Network Tags for how to assign custom tags in Gremlin.
Zone tags are required for the Zone Reliability Test.
To discover any dependencies associated with your Services, the Gremlin agent must be configured to collect process data by enabling Process Collection. When Process Collection is active, the Gremlin Agent collects process information from hosts, containers, and Kubernetes objects.
To test the reliability of a Service, you will need to add at least one Golden Signal monitor to your Service definition. Gremlin recommends a combination of 3 to 5 monitors for a well-rounded view of your Service’s health. To integrate a Golden Signal monitor with a Service definition, you need the URL of the monitor and the API key. See Adding a Golden Signal monitor to a Service for detailed steps.
To integrate Gremlin with anything on a private network, you need to install Gremlin's Integration Agent, in addition to installing the Gremlin Agent. The Gremlin Integration Agent allows you to integrate Gremlin with your internal tools without exposing your internal endpoints to the public Internet.
Golden Signal integrations originate from the following IP address:
Ensure that this IP address is on your firewall's allow list so that Golden Signal monitor integrations are not blocked.