> ## Documentation Index > Fetch the complete documentation index at: https://docs.vortexiq.ai/llms.txt > Use this file to discover all available pages before exploring further. # DigitalOcean on Vortex IQ > Monitor DigitalOcean health, cost and reliability signals, and catch incidents and runaway spend early. Monitor DigitalOcean health, cost and reliability signals, and catch incidents and runaway spend early. [Connect or manage this source](https://app.vortexiq.ai/workbench/settings/sources) · [How connecting works](/integrations/connector-catalogue) · [Create a workflow](https://app.vortexiq.ai/workbench/flows/create?connector=digitalocean) performance signals automated checks automated fixes workflows API operations ### What you can achieve Capabilities are grouped around merchant outcomes, not API terminology. Monitor orders, fulfilment, delivery and settlement. Keep tracking, access and change under governed control. Identify missing, inconsistent or outdated product data. ### From connection to verified outcome The controlled sequence every capability follows. Nothing changes a connected system without the approval step. Authorise the source. Scopes are shown before access is granted. Watch the signals against your own baselines, not universal defaults. Run checks and gather evidence specific to your store. Explain what happened, why it matters and the proposed action. You review scope, risk and reversibility before anything changes. Apply through governed connector operations. Confirm the intended result and keep the receipt. No changes are made without the configured approval policy. Read-only operations do not modify the connected system; schedules, access scopes, API usage and data handling remain governed by Vortex IQ controls. ### Monitor performance 28 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system. | Signal | Alert behaviour | What it tracks | | ---------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Account Balance** | Watch only | account\_balance field from GET /v2/customers/my/balance (a negative value means credit owed by the customer, positive means credit remaining). | | **Account Status Alert** | Watch only | account.status field from GET /v2/account; flags when not 'active' (e.g. 'warning' or 'locked', which blocks provisioning and can indicate a billing o | | **Active Droplets** | Watch only | Count of droplets\[] with status == active from GET /v2/droplets. | | **Billing Events (30d)** | Watch only | Count of billing\_history\[] entries with date >= 30 days ago from GET /v2/customers/my/billing\_history. | | **Block Storage Volumes** | Watch only | Count of volumes\[] from GET /v2/volumes. | | **Databases by Engine** | Watch only | databases\[] grouped by engine from GET /v2/databases. | | **Kubernetes Clusters** | Watch only | Count of kubernetes\_clusters\[] from GET /v2/kubernetes/clusters. | | **Kubernetes Clusters by Version** | Watch only | kubernetes\_clusters\[] grouped by version from GET /v2/kubernetes/clusters. | | **Load Balancers Total** | Watch only | Count of load\_balancers\[] from GET /v2/load\_balancers. | | **Managed Databases** | Watch only | Count of databases\[] from GET /v2/databases. | | **Month-to-Date Spend** | Watch only | month\_to\_date\_balance field from GET /v2/customers/my/balance (spend accrued so far this billing cycle). | | **Month-to-Date Usage** | Watch only | month\_to\_date\_usage field from GET /v2/customers/my/balance. | | **Most Recent Invoice** | Watch only | amount field of the most recent entry in invoices\[] (sorted by invoice\_period desc) from GET /v2/customers/my/invoices. | | **Previous Invoice** | Watch only | amount field of the second-most-recent entry in invoices\[] from GET /v2/customers/my/invoices; the comparison base for the spend trend. | | **Spend Spike Alert** | Alert band 10 / 50 | Same calculation as dig\_spend\_trend (invoices\[] latest vs prior amount); duplicated into the Alerts section so it fires as a tunable Alert Rule. | | **Spend Trend vs Last Cycle** | Alert band 10 / 50 | Percent change between the two most recent entries in invoices\[] (sorted by invoice\_period desc) from GET /v2/customers/my/invoices: (latest amount - | | **Total Database Nodes** | Watch only | SUM(num\_nodes) across databases\[] from GET /v2/databases. | | **Total Volume Size (GB)** | Watch only | SUM(size\_gigabytes) across volumes\[] from GET /v2/volumes. | | Signal | Alert behaviour | What it tracks | | --------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Cloud Health Score** | Alert band 90 / 70 | 0-100 composite over whatever is readable: token valid (100) + account.status == active (100/0) from GET /v2/account + pct of droplets\[] with status = | | **Droplets Total** | Watch only | Count of droplets\[] from GET /v2/droplets. | | **Droplets by Region** | Watch only | droplets\[] grouped by region.slug from GET /v2/droplets. | | **Droplets by Size** | Watch only | droplets\[] grouped by size\_slug from GET /v2/droplets. | | **Load Balancers Not Active** | Watch only | Count of load\_balancers\[] with status != active (e.g. new or errored) from GET /v2/load\_balancers. | | **Locked Droplets** | Watch only | Count of droplets\[] with locked == true from GET /v2/droplets; a locked droplet cannot take new actions (resize, power-cycle) until the current action | | **Total Memory Provisioned (GB)** | Watch only | SUM(memory) across droplets\[] from GET /v2/droplets, converted from MB to GB (memory / 1024). | | **Total vCPUs Provisioned** | Watch only | SUM(vcpus) across droplets\[] from GET /v2/droplets. | | Signal | Alert behaviour | What it tracks | | ---------------------------------------- | --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ | | **Cost by Product (Latest Invoice)** | Watch only | amount from invoice\_items\[] grouped by product for the most recent invoice\_uuid, via GET /v2/customers/my/invoices/{invoice_uuid}; top 10 products. | | **Top Product by Cost (Latest Invoice)** | Watch only | The single largest product by amount from the most recent invoice's invoice\_items\[]; the product name is the card detail. | ### Audit risks and opportunities A fix status appears only where the action, inputs, approval, verification and recovery controls are mapped. Candidate remediations are never executable. Open a check for the detail. **Severity** high · **Outcome** Control risk and change · **Fix status** Report only Once this credential fails, VortexIQ stops seeing usage, cost and health data from this platform entirely, and every finding here that depends on it goes stale from that moment, silently, until someone notices the numbers stopped updating. Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps. Reference: `CLOUD-AUTH-001` **Severity** high · **Outcome** Run operations · **Fix status** Report only Spend on this platform rose more than 50% versus the prior period. A jump this size is either a deliberate scale-up worth confirming was intentional, or an unbounded process, a stuck job, a misconfigured autoscaler, quietly running up a bill nobody approved. Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps. Reference: `CLOUD-SPEND-001` **Severity** medium · **Outcome** Control risk and change · **Fix status** Report only Usage halving against the prior period is the earliest sign of a silent stall: a broken schedule, an expired credential, or a team that quietly stopped. Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps. Reference: `CLOUD-USAGE-001` #### Build your own automated fixes Turn any finding into an automated fix with a Vortex IQ workflow: **over 13,000 read and write operations across more than 200 connectors** are available as building blocks, with approval, verification and rollback on every change. ### Automate approved work Vortex IQ is integrated with **10 read** and **0 write** operations across customer myinvoices, accounts, customer mybalances, customer mybillinghistorys, databas, droplets on DigitalOcean. Combine them with anything from the **over 13,000 operations across more than 200 connectors** to automate the work in your own words. Changes follow your configured approval policy: the target, proposed change, affected records, risk, reversibility and verification plan are shown before execution. [Create a workflow](https://app.vortexiq.ai/workbench/flows/create?connector=digitalocean) #### Ready to build your first DigitalOcean workflow Pick a trigger, add the operations above as steps, and every step that changes data pauses for your approval. Monitoring and audits are live now and can start any workflow you build. | Resource | Read operations | Write operations | | -------------------------- | --------------- | ---------------- | | customer myinvoices | 2 | 0 | | accounts | 1 | 0 | | customer mybalances | 1 | 0 | | customer mybillinghistorys | 1 | 0 | | databas | 1 | 0 | | droplets | 1 | 0 | | kuberneteclusters | 1 | 0 | | loadbalancers | 1 | 0 | Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.