Digital Ocean

You use Digital Ocean as a cloud provider to build your services on? Do not stay in the dark and use this application to track the availability of these services into your monitoring tool. This Digital Ocean application brings you the availability status of the platform services (API, Billing, DNS, Support Center...) and of each service family (Droplets, Kubernetes, Volumes, Spaces, the AI services...), across every region DigitalOcean operates.

Options

• Name*: Just a simple label to find it easier in the SenHub's interface
• Description: Description for your own usage only.
• Group: optional — assign this instance to a group to organise it within SenHub.
• Representation*: How much of the status page becomes channels. See Choosing a representation below.
• Filter*: None, Include or Exclude. Keeps or drops channels by name.
• Filter expression: required when the filter is Include or Exclude. One or more patterns, separated by ; or ,, with * and ? as wildcards.

Choosing a representation

DigitalOcean's status page has two layers: a handful of components that describe the platform as a whole — API, Billing, DNS, Support Center — and seventeen sections, such as Droplets, Volumes or Kubernetes, each listing its own regions. Spelled out in full that is well over two hundred components, more than most monitoring tools accept on a single sensor.

The platform-wide components are always returned. The representation decides what the sections contribute:

Representation	What you get	Channels
All services and regions	every component, named (Section) Region	~240
One channel per region	each region, across all sections	~47
One channel per section	each section as a whole	~28
Platform services only	nothing from the sections	~11

All is the default because it is the view that shows you every name. Look at it once, decide what you actually care about, then narrow it down with the filter — or pick a coarser representation.

A section reports the status DigitalOcean computes for it, which is the status of its most degraded component. A region reports its most degraded occurrence across every section. In both cases a single degraded datacenter turns the channel, so nothing is hidden by the summary.

Filtering channels

The filter applies to the channel name as it appears in the output, wildcards included, and it is not case-sensitive.

Representation	Filter	Expression	Result
All services and regions	Include	*FRA1	every service hosted in Frankfurt
All services and regions	Include	(Droplets)*	the Droplets section, region by region
One channel per section	Exclude	Spaces*;VPC	every section except Spaces, Spaces CDN and VPC

If the filter matches nothing, the connector reports an error listing the channels that were available, rather than returning an empty result that would read as a platform without any incident.

Example output

With the default representation, an excerpt:

{
  "metrics": [
    { "channel": "API", "value": "Operational" },
    { "channel": "Billing", "value": "Operational" },
    { "channel": "DNS", "value": "Operational" },
    { "channel": "(Agentic Inference Cloud) Inference", "value": "Operational" },
    { "channel": "(Droplets) FRA1", "value": "Operational" },
    { "channel": "(Droplets) NYC3", "value": "Degraded Performance" },
    { "channel": "(Volumes) FRA1", "value": "Operational" },
    { "channel": "(Kubernetes) FRA1", "value": "Operational" }
  ],
  "message": "Metrics successfully retrieved.",
  "status": "OK",
  "date": 1725981405127
}

Values are reported exactly as DigitalOcean words them, the usual ones being Operational, Degraded Performance, Partial Outage, Major Outage and Under Maintenance.

The channel list follows the vendor's page: when DigitalOcean adds a service or opens a region, it is picked up on its own at the next collection. If the page itself becomes unreadable, the connector reports an error rather than an empty list.