One read-only personal access token turns every droplet into an ordinary SmartTile device — droplet status, CPU, memory, disk and public bandwidth from the Monitoring API, uptime history, billing and firewall posture — alerting and ticketing in the IT Service Management (ITSM) system your team already uses.
Droplets are easy to spin up and easy to forget: they rarely sit behind the customer's firewall, and their health lives in the DigitalOcean control panel. SmartTile CloudAutomate reads the team with a token that has only read scopes, makes each droplet a device, and lets the status DigitalOcean reports on this poll decide UP or DOWN — a droplet that is powered off, or that disappears from the list, is not left green.
Every droplet (or those in the regions you list) imported one-to-one under a "DigitalOcean nyc3"-style location, with size slug, vCPU, memory, disk, image, tags and public/private IPv4.
Droplet status every 60 s: active is UP; off, archived, or missing from the list is DOWN after two polls. Every change lands in state history and the Uptime chart.
CPU busy %, memory used, filesystem used, public inbound/outbound bandwidth, every 5 min — feeding Device Health thresholds and the Bandwidth chart. Memory and disk need the DigitalOcean metrics agent.
Month-to-date usage and account balance, the last 12 invoices by month, and the current invoice preview as the month's forecast — on the Spend tab, cached hourly.
Droplets with no Cloud Firewall, firewall rules opening 22/3389/3306/5432/6379/27017 or all to the internet, droplets with backups off or no metrics agent.
If the token is revoked or expires, its droplets turn UNKNOWN after ~6 minutes and the NOC gets one e-mail. A droplet's age is never shown as its uptime.
SmartTile CloudAutomate, expiry 1 year, Custom Scopes — tick only the scopes listed.dop_v1_) — it is shown once.nyc3, sfo3) or a name/tag filter, then Save & Test. Pick droplets from the import table and import.| Scope | Token scopes |
|---|---|
| Monitoring | account:read, droplet:read, monitoring:read, regions:read |
| Inventory | vpc:read, image:read, snapshot:read |
| Spend | billing:read |
| Security | firewall:read |
/v2/accountSave & Test: proves the token, names the team/v2/dropletsDiscovery (daily) and every status poll, paged 200 at a time/v2/regionsRegions available to the team/v2/monitoring/metrics/droplet/cpuCPU seconds per mode → busy %/v2/monitoring/metrics/droplet/memory_*memory_total + memory_available → used %/v2/monitoring/metrics/droplet/filesystem_*filesystem_size + filesystem_free → used %/v2/monitoring/metrics/droplet/bandwidthPublic interface, inbound and outbound/v2/customers/my/balanceMonth-to-date usage and account balance/v2/customers/my/invoicesLast 12 invoices + current invoice preview/v2/firewallsWhich droplets each Cloud Firewall covers + inbound rulesDevice: api-01 · s-2vcpu-4gb · Location "DigitalOcean nyc3"
Seen by SmartTile: droplet status off on two polls in a row → DOWN
Then: the company's normal ticket path — Rev.io or the connected ITSM system — and Open in DigitalOcean on the device card goes straight to the droplet
SmartTile asks only for :read scopes and never calls a write endpoint on DigitalOcean. The token format (dop_v1_…) is checked before saving.
The token is encrypted at rest when saved and never returned by the API — only whether one is stored.
Each company connects its own team; every CloudAutomate call is fenced to the caller's organization, and adding or testing a token needs an admin.
Region, name and tag filters apply before discovery; the import table shows exactly what will be created or updated.
Engine, status sync, health metrics, spend and security each have their own Engine Safety switch, plus a global kill switch.
Token created, tested, updated or deleted and every import are written to the activity log; every sync to the Connections tab log.
| Question | Answer |
|---|---|
| Can SmartTile open a DigitalOcean support ticket? | No. DigitalOcean publishes no support-ticket API, so SmartTile does not pretend to — the ticket goes to your ITSM system and the engineer opens DigitalOcean support by hand. |
| Why is memory blank? | DigitalOcean only reports memory and disk from its metrics agent (Droplet → Monitoring → install). CPU, bandwidth and status work without it — and a missing agent is itself listed as a finding. |
| Managed databases, Kubernetes, App Platform? | Not today — droplets only. |