Monitoring Overview

Plans and Pricing

DigitalOcean Monitoring is provided at no additional cost.

Regional Availability

Monitoring is available in all regions. The DigitalOcean metrics agent must be installed on all participating Droplets.


The DigitalOcean metrics agent is an open-source Go utility that forwards basic metrics about your Droplet to the DigitalOcean metrics backend.

Without the metrics agent, Droplet graphs only display information about public and private bandwidth usage, CPU usage, and disk I/O. With the metrics agent, you gain access to DigitalOcean Monitoring features, such as:

  • Additional graphed metrics: System and user CPU usage, memory usage, disk read, disk write, disk usage, incoming and outgoing public bandwidth, incoming and outgoing private bandwidth
  • Alert-capable metrics: CPU, incoming bandwidth, outgoing bandwidth, disk read, disk write, memory usage, disk usage
  • Notification methods: Email and Slack

The metrics agent currently supports Ubuntu 14.04 and higher, CentOS 6 and higher, Debian 8, and Fedora 28.

In preparation for the deprecation of our initial metrics agent, DigitalOcean has released a beta metrics agent that uses the Prometheus node_exporter codebase. The new agent makes it easier for users to contribute custom metrics, adds an additional load average plot, supports Fedora 27, allows users to opt out of process name collection, and will be the default agent used by our managed databases and Kubernetes products. Learn more in the metrics agent repo.

To use the new agent during the beta period, you can upgrade Droplets running the current agent. In mid-2019, we plan to fully deprecate the initial metrics agent, at which point you’ll have three months to switch to the new agent. We’ll announce this deprecation in our release notes.

What Can the Metrics Agent Access?

The metrics agent service runs as an unprivileged user with access to only three directories:

  • /proc: Where the metrics agent collects data about the current state of the system
  • /var/opt: Where the metrics agent writes its authentication information
  • /opt/digitalocean: The binary’s home directory

The metrics agent also reports the process names to the metrics endpoint, which DigitalOcean uses internally in aggregate to help guide product priorities. It does not report on environmental variables or process arguments to avoid exposing potentially sensitive information.

The new agent gives you the option to opt out of process name collection. Refer to the metrics agent installation documentation for instructions.

How Does the Metrics Agent Send Metrics?

The DigitalOcean metrics agent uses ports 80 and 443 for outgoing data. Inbound access is not required. Since the metrrics agent only uses the ports for outbound data, you can safely run a web server without interference.

Port 80 is used to contact the DigitalOcean metadata service to obtain an authentication token. The metrics agent uses this token to authenticate to the metrics backend and encrypt its transmissions.


  • It is not possible to revert to the original graphs once the metrics agent has been enabled.

  • You cannot add or change the alert email address for an individual account.

  • Alerting is not yet available for load average.