Bobcares

Allowlist The DigitalOcean Metrics Agent With Firewall | All About

PDF Header PDF Footer

Read the article to know more about how to allowlist the DigitalOcean Metrics agent with a firewall. With our DigitalOcean Managed Services, Bobcares offers solutions to your DigitalOcean Monitoring issues.

How To Allowlist The DigitalOcean Metrics Agent With Firewall?

The DigitalOcean Metrics Agent collects statistics on Droplet-level resource usage. To assist us in monitoring the operational health of the infrastructure, it offers extra Droplet graphs and enables customizable metrics alert policies with integrated email and Slack notifications. It also enables extended metrics and enhanced monitoring features,

In order to shield the servers from external attacks, firewalls stand between them and other computers on the network. However, they may also obstruct the DigitalOcean Metrics Agent from accessing the Droplet. Both the local firewalls defending the Droplet and the Cloud Firewall service provided by DigitalOcean fall under this category. The metrics agent must be allowed access to the monitoring service through whichever firewall we employ in order for the metrics data from the Droplet to be reported to the monitoring service.

In order to enable the Metrics Agent, we need to select the Monitoring checkbox in the additional options section of the creation page during a droplet creation. During the Droplet creation process, the metrics agent will be immediately installed and enabled.

DigitalOcean Metrics Agent – Firewall Setup

Ports 80 and 443 on the Droplet are used by the Metrics Agent to connect to DigitalOcean. We must set up rules in the firewall to permit all outgoing IPv4 and IPv6 HTTP/HTTPS traffic over ports 80 and 443 in order to permit the metrics agent to connect through the firewall.

For Ubuntu and Debian systems, UFW or Firewalld can be used to generate these rules. For CentOS and Fedora systems, use Firewalld. These services communicate with iptables, a firewall application built into the majority of Linux operating systems. Although it is best to use UFW or FirewallD since they are more user-friendly, we may still configure these firewall rules directly in iptables.

Also, when using the Cloud Firewall provided by DigitalOcean, we must set up firewall rules to allow all outgoing IPv4 and IPv6 HTTP/HTTPS traffic on ports 80 and 443.

[Are you looking for a solution to another query? We are just a click away.]

Conclusion

To conclude, the article provides a simple guide on how to allowlist the DigitalOcean Metrics agent with a firewall.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Bobcares

Use your time to build great apps. Leave your servers to us.

Managing a server is time consuming. Whether you are an expert or a newbie, that is time you could use to focus on your product or service. Leave your server management to us, and use that time to focus on the growth and success of your business.

TALK TO US Or click here to learn more.

Speed issues driving customers away?
We’ve got your back!

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie
_clck, _clsk, CLID, ANONCHK, MR, MUID, SM

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

_reb2bgeo - The visitor's geographical location

_reb2bloaded - Whether or not the script loaded for the visitor

_reb2bref - The referring URL for the visit

_reb2bsessionID - The visitor's RB2B session ID

_reb2buid - The visitor's RB2B user ID

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid
_reb2bgeo, _reb2bloaded, _reb2bref, _reb2bsessionID, _reb2buid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF