DigitalOcean Integration
Monitor Droplets, managed Kubernetes clusters, managed databases, and App Platform deployments across your DigitalOcean account. Unified cloud observability with no agents required.
How It Works
Connect Your DigitalOcean Account
Create a read-only DigitalOcean API token with the Monitoring scope. TigerOps uses the DigitalOcean Monitoring API and Metrics API to pull Droplet, DOKS, and managed database metrics without installing agents.
Auto-Discover Resources
TigerOps enumerates all Droplets, Kubernetes clusters, managed databases, and Spaces buckets in your account. Resources are tagged automatically using your existing DigitalOcean tags and project assignments.
Deploy the DOKS Agent
For deep Kubernetes visibility, deploy the TigerOps DaemonSet to your DOKS cluster with a single kubectl apply command. It collects pod-level metrics, logs, and traces beyond what the Monitoring API provides.
Set Resource-Aware Alerts
TigerOps learns your resource utilization patterns and sets adaptive thresholds. Alerts fire before you hit plan limits, with AI-generated recommendations for right-sizing Droplet plans.
What You Get Out of the Box
Droplet CPU & Memory
Per-Droplet CPU utilization, memory usage, disk I/O, and network throughput. Group by tag, project, or region. TigerOps alerts on sustained resource pressure before performance degrades.
DOKS Kubernetes Metrics
Full Kubernetes observability for DigitalOcean Kubernetes clusters: node pressure, pod health, deployment rollout status, and HPA scaling events with correlated metric context.
Managed Database Health
Connection counts, query latency, replication lag, and storage utilization for managed PostgreSQL, MySQL, Redis, and MongoDB clusters on DigitalOcean.
App Platform Metrics
Request latency, error rates, and instance scaling events for DigitalOcean App Platform deployments. Correlated with deploy events from the DigitalOcean API.
Load Balancer Analytics
Request rate, active connections, health check status, and backend response distribution for DigitalOcean Load Balancers. Identify unhealthy backend Droplets instantly.
Network & Bandwidth Monitoring
Inbound and outbound bandwidth per Droplet, bandwidth limit warnings, and regional network latency. TigerOps alerts before you exceed bandwidth limits or incur overage charges.
DigitalOcean API Token Setup
Connect TigerOps to your DigitalOcean account using a read-only API token with the Monitoring scope.
# Step 1: Create a read-only DigitalOcean API token
# Navigate to: https://cloud.digitalocean.com/account/api/tokens
# Scopes required: read (Monitoring, Droplet, Kubernetes, Databases)
# Step 2: Configure TigerOps with the token
export TIGEROPS_API_KEY="your_tigerops_api_key"
export DO_API_TOKEN="dop_v1_your_readonly_token"
curl -X POST https://api.atatus.net/v1/integrations/digitalocean -H "Authorization: Bearer ${TIGEROPS_API_KEY}" -H "Content-Type: application/json" -d '{
"api_token": "'"$DO_API_TOKEN"'",
"collect_droplets": true,
"collect_kubernetes": true,
"collect_databases": true,
"collect_load_balancers": true,
"collect_spaces": true,
"tag_filters": [],
"regions": ["nyc3", "ams3", "sgp1"]
}'
# Step 3: For DOKS deep monitoring — deploy the TigerOps agent
doctl kubernetes cluster kubeconfig save my-cluster
kubectl apply -f https://install.atatus.net/doks/tigerops-agent.yaml
# Step 4: Pass your API key as a Kubernetes secret
kubectl create secret generic tigerops-secret --from-literal=api-key="${TIGEROPS_API_KEY}" -n tigerops-systemCommon Questions
Does TigerOps require installing an agent on every Droplet?
No. TigerOps uses the DigitalOcean Monitoring API for agentless Droplet metrics. For deeper visibility including process-level metrics and distributed tracing, you can optionally install the lightweight TigerOps agent, but it is not required for core monitoring.
Can TigerOps monitor multiple DigitalOcean teams or accounts?
Yes. TigerOps supports connecting multiple DigitalOcean API tokens from different teams or accounts. Resources from all accounts appear in a unified dashboard with account-level labeling for easy filtering.
Does TigerOps support DigitalOcean Spaces object storage monitoring?
Yes. TigerOps monitors DigitalOcean Spaces request rates, storage utilization, and bandwidth usage through the S3-compatible API metrics endpoint.
How does TigerOps handle DigitalOcean region-specific monitoring?
TigerOps automatically labels all metrics with the DigitalOcean region slug (e.g., nyc3, ams3, sgp1). You can filter dashboards and alerts by region, compare resource utilization across regions, and track latency from different geographic locations.
Can TigerOps alert me before I hit my DigitalOcean bandwidth limit?
Yes. TigerOps tracks monthly bandwidth consumption as a percentage of your plan limit and fires predictive alerts when the usage trajectory will exceed the limit before the billing cycle resets. This gives you time to upgrade or optimize before incurring overage charges.
Full Visibility Into Your DigitalOcean Infrastructure
No credit card required. Connect in minutes. Droplet, Kubernetes, and database metrics immediately.