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.

Features

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

On 8 April, 2019, we released a new Prometheus-based metrics agent into production. All agent installations on or after this date will receive the new agent by default. On 8 July, 2019, the legacy metrics agent will be deprecated, meaning users will no longer be able to view metrics from Droplets running the legacy agent. You can upgrade to the new agent at any time.

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 additional metrics, including load average (1-, 5-, and 15-minute), memory usage, and disk usage.

With the agent, metrics-based alerting is also enabled for total CPU usage, incoming bandwidth, outgoing bandwidth, disk read, disk write, memory usage, and disk usage. Alert notifications may be sent via email and/or Slack.

The metrics agent currently supports the following operating system versions:

  • Ubuntu 14.04 and higher
  • CentOS 6 and higher
  • Debian 8 and higher
  • Fedora 27 and higher

There is also the option to run the agent as a Docker container.

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. However, you can still opt out of process name collection.

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.

Limitations

  • 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.