I’d really like to install and get DigitalOcean’s Agent feature working on one of my droplets that has inbound rules. Is there some static IP that I can post in as the source?
The DigitalOcean monitoring agent should not need inbound firewall rules to function. Though it does require outbound TCP access on ports 80 and 443 to authenticate to the Monitoring service and to send metrics.
The agent need to be able to access the DigitalOcean metadata API at: http://169.254.169.254/metadata/v1/ as well as the metrics service itself at https://sonar.digitalocean.com. Additionally, in order to allow the agent to update itself https://repos.sonar.digitalocean.com
You can find their current IP addresses using: dig +short sonar.digitalocean.com and dig +short repos.sonar.digitalocean.com on the command line. Currently those are 162.243.188.200 and 151.101.21.7 respectively.
Great info! What about installing? When I try the install script curl -sSL https://agent.digitalocean.com/install.sh | sh it can’t resolve.
That script is hosted in another location, currently 151.101.188.233 Though you can avoid creating a separate rule for it by checking the box for “Monitoring” when you create a Droplet. That will automatically install the agent on the new Droplet.
Essentially, all the script does is configure the appropriate repo based on the operating system. For instance on Ubuntu, it creates the file /etc/apt/sources.list.d/digitalocean-agent.list with the contents:
deb https://repos.sonar.digitalocean.com/apt main main
Then runs apt update; apt install -y do-agent
Brilliant! Thank you! I was able to get it working with your help!
Just one comment, the IP addresses may resolve differently in future and/or in different geographic locations. So just keep an eye on double-checking those when performing any necessary updates in future.