Cost and budgets

OpsNexus collects daily cost from every connected cloud account and shows it on the Cloud overview pages and on Cloud > Cost & budgets. Cost data arrives with each account sync. See Cloud accounts to connect accounts.

You need read access to the Cloud module to see cost, and modify access to add or delete budgets.

#Where cost data comes from

Each sync re-reads the last 90 days (CLOUD_COST_DAYS) and replaces the stored days, so corrections from the provider show up.

If cost cannot be read, the account still syncs its resources, and the reason is shown under the account status. For example: "Cost Management: HTTP 403 (grant Cost Management Reader)".

#Usage before credits

All totals, budgets and charts show usage before credits. AWS promotional credits would otherwise cancel each service out and every budget would read 0%.

Credits are shown on their own:

• The Cost this month tile shows credits and the amount to pay when there are credits.
• The cost explorer shows Credits & refunds and Net to pay when grouped by service.

#Currency

Amounts are stored in the currency the provider returns. Budgets and most views use USD.

#Cloud overview

Cloud > Overview covers all clouds. Cloud > AWS, Azure, Google Cloud and Oracle Cloud show the same view for one cloud.

Lists of amounts hide rows that round to zero and say how many were hidden.

#Cost & budgets page

Open Cloud > Cost & budgets. The Cloud selector at the top applies to the whole page: budgets, cost explorer, VPC cost and suggestions. The choice is kept in the URL (for example ?cloud=azure), so you can share the link.

If you choose a cloud with no connected account, the page says so and offers a button to connect one.

#Cost explorer

The Cost explorer card shows cost for any period:

1. Set From and To.
2. Choose Group by: Service, Cloud (only when all clouds are selected), Region, Account or Day.

The card shows the Usage for the period, and when grouped by service, Credits & refunds and Net to pay. The bars show the top 25 rows. Click Export CSV to download every row.

#Download a cost report

Click Download report to get a cost report as PDF or Excel:

• Period: Last 7, 15, 30 or 90 days.
• Cloud: All clouds or one cloud.

The report has totals (usage before credits, credits and refunds, net to pay) with a daily chart, cost by cloud, region, service and account, and for AWS, cost by VPC and by resource. The PDF lists the top 150 resources; the Excel file lists all of them.

#Budgets

A budget is a monthly amount for a scope. OpsNexus compares it with this month's usage and alerts you as spending crosses thresholds.

#Add a budget

In the Budgets card:

1. Enter a Budget name.
2. Enter the Monthly amount (USD).
3. Choose the scope:
   • Cloud: all clouds or one cloud.
   • Account: all accounts, or one account. Choosing an account also sets its cloud.
   • Service (optional): all services, or one service seen in the last 90 days.
4. Click Add budget.

The budget is checked straight away.

#Budget table

Budgets are monthly and reset on the 1st. To change a budget, delete it and add a new one. Deleting a budget does not affect your cloud costs.

#Budget alerts

Budgets alert at 50%, 80% and 100% of the monthly amount.

• Budgets are checked after every account sync and when a budget is created.
• When spend crosses a threshold, OpsNexus sends the Cloud cost alert notification event, for example "Budget production at 82.4% (80% threshold)". The message includes the amount spent and the forecast.
• Each threshold alerts once per month. If spend jumps past several thresholds between checks, only the highest one alerts.
• Alerts at 100% have high severity. Lower thresholds have medium severity.

Alerts are based on actual spend, not on the forecast.

To receive the alerts, subscribe a channel to Cloud cost alert in Notifications.

#Cost by VPC (AWS)

The Cost by VPC · AWS card splits AWS cost by the VPC each resource sits in. It appears when All clouds or AWS is selected. For other clouds the card says cost by network is not available yet.

It uses AWS per-resource cost, which needs:

• the ce:GetCostAndUsageWithResources permission, and
• Resource-level data at daily granularity turned on in AWS Billing and Cost Management preferences.

AWS keeps per-resource cost for only 14 days. OpsNexus stores each day it reads, for up to 400 days (CLOUD_RESOURCE_COST_RETENTION_DAYS), so longer periods fill up over time. The card says from which date per-resource cost is available.

#Overview

Choose a Period (Last 7, 15, 30 or 90 days). With VPC set to All VPCs (overview), the card shows:

The table lists each VPC with its Region, Resources, Top services, cost and Share of the total.

#One VPC

Pick a VPC to see:

• Resource map: subnets by availability zone (public or private), route tables, and connections to other networks (internet, NAT, transit and VPN gateways, peering connections, VPC endpoints). Subnet cost is the cost of the resources inside it. Load balancers and databases that span several subnets are split evenly.
• By service: cost and count per service.
• Resources: every resource with its service, region, subnet, state and cost. Filter by Service or by clicking a subnet, and click Export CSV to download the list.

#Warnings on this card

• An AWS account that cannot be read: OpsNexus cannot see names, subnets or VPCs, so costs show raw IDs.
• AWS accounts in your billing that are not connected: their resources sit under Other billed resources. Connect each one with its own read-only key or role.
• No per-resource cost yet: the reason from AWS is shown, with the steps above.

#Savings suggestions

The Savings suggestions card lists simple findings for the selected cloud:

Suggestions appear once accounts have synced resources and cost.