Skip to main content
A Mac that runs the CostGraph Agent appears on the Virtual Machines page next to your other machines. CostGraph shows the details a Mac reports and leaves out the charts that only Linux hosts produce.

Find your Macs

A Mac you own lists Apple as its provider. A Mac you rent from a cloud keeps that cloud as its provider, such as AWS for an EC2 Mac. The Apple mark next to the type identifies every Mac, whoever hosts it. The Type column shows the chip of a Mac you own, such as Apple M4 Pro, with Owned as its pricing model. A rented Mac shows the instance type and pricing model its cloud bills. For a Mac you own, the line under its name shows its model. After your organization adds a Mac, the list shows four filters:
  • Platform selects Macs or Linux hosts.
  • Chip selects a chip, such as Apple M2.
  • Model selects a model, such as Mac mini.
  • macOS version selects a macOS release.
The filters scope the list, VM spend, and the top contributors.

Mac details

The header shows the Mac’s CPU cores and Unified memory. The tabs are Overview and Metrics. Overview shows the Mac’s Model, Chip, macOS version, and Darwin version among its details. A Mac you own has no instance type, region, or usage type, so those details are left out.

Cost basis

CostGraph prices a Mac you own from its model’s list price in the CostGraph price catalog. The price is spread over the months the catalog sets for that model. The Cost basis detail on the overview names the source of the hourly cost: Cost / hour shows the hourly cost CostGraph assigns to the Mac. To cost a Mac at your own figure, such as what you paid or a hosting contract, assign it one of your organization’s prices. Set the Price field on the Mac’s overview, or tag the Mac with a pricing ID through the API. The Mac is costed at that price from the next hour, and Cost basis reads Your pinned price. See Assign a price to a virtual machine.

Memory pressure and thermal state

Two cards under System cost show the Mac’s latest memory pressure and thermal state, as macOS reports them: The memory pressure card also shows the Mac’s unified memory. A card reads Not reported by this Mac yet until the agent sends its first reading. The usage heatmap adds Memory pressure and Thermal tabs beside CPU and Memory. Each cell shows the worst level the Mac reached in that hour, so a short spike is not hidden by a calm hour around it. Every level except the calm one carries a pattern, so the grid reads without color. Hottest window names the hour with the worst level and that level.

Metrics on a Mac

Metrics charts the same ranges as for other machines. Memory is labeled unified memory, disk usage is the APFS container, and network traffic counts physical interfaces only. macOS does not report the following, so the Mac pages leave them out:
  • The Containers and GPUs tabs, and the container runtime and running containers details.
  • The GPU section of Metrics.
  • CPU steal, IO wait, and interrupt time.
  • CPU, memory, and IO pressure stall charts. Memory pressure takes their place.
  • Disk throughput, IO operations, IO latency, and busy time.
  • Buffered and cached memory, and TCP retransmits.
When you compare a Mac with a Linux host in Metrics, CostGraph shows every chart. The charts a Mac does not report show no data for the Mac.

Next steps

Virtual machines

The fleet view, recommendations, and the details every machine shares.

Pricing IDs

Register your own rates and assign them to machines.