best-action-5428
11/18/2022, 7:26 AMversion: 0.1
resource_usage:
azurerm_managed_disk.DATA[0]:
monthly_disk_operations: 100000000
....
result using the usal file . anything created using a index isn't considered although I saw no warning.
Name Monthly Qty Unit Monthly Cost (CAD)
azurerm_linux_virtual_machine.curavm
├─ Instance usage (pay as you go, Standard_M8ms) 750 hours $1,693.75
└─ os_disk
├─ Storage (S4) 1 months $2.26
└─ Disk operations 10,000 10k operations $6.68
azurerm_managed_disk.BIN
├─ Storage (S10) 1 months $8.65
└─ Disk operations 10,000 10k operations $6.68
azurerm_managed_disk.DATA[0]
└─ Storage (P20) 1 months $97.83
...etc
busy-agent-35515
11/18/2022, 9:40 AMcuravm
resource, however DATA[0]
is clipped, I assume it doesn't list the Disk operations cost.best-action-5428
11/18/2022, 5:34 PMbusy-agent-35515
11/20/2022, 4:23 PMbest-action-5428
11/22/2022, 7:16 PMbusy-agent-35515
11/22/2022, 7:26 PMThe total cost of Premium SSDs depends on the size and number of the disks, and will be affected by the number of outbound data transfers.
best-action-5428
11/22/2022, 7:28 PMbusy-agent-35515
11/22/2022, 7:29 PMbest-action-5428
11/22/2022, 7:29 PMinfracost breakdown --sync-usage-file --usage-file infracost-usage.yml --path /code
this is what I have in the usage yml :
# resource_usage:
##
## The following usage values apply to individual resources and override any value defined in the resource_type_default_usage section.
## All values are commented-out, you can uncomment resources and customize as needed.
##
# azurerm_managed_disk.DATA[0]:
# monthly_disk_operations: 0 # Number of disk operations (writes, reads, deletes) using a unit size of 256KiB.
# azurerm_managed_disk.DATA[1]:
# monthly_disk_operations: 0 # Number of disk operations (writes, reads, deletes) using a unit size of 256KiB.
# azurerm_managed_disk.DATA[2]:
# monthly_disk_operations: 0 # Number of disk operations (writes, reads, deletes) using a unit size of 256KiB.
# azurerm_managed_disk.DATA[3]:
# monthly_disk_operations: 0 # Number of disk operations (writes, reads, deletes) using a unit size of 256KiB.
# azurerm_managed_disk.DATA[4]:
# monthly_disk_operations: 0 # Number of disk operations (writes, reads, deletes) using a unit size of 256KiB.
# azurerm_managed_disk.RECO[0]:
# monthly_disk_operations: 0 # Number of disk operations (writes, reads, deletes) using a unit size of 256KiB.
# azurerm_managed_disk.RECO[1]:
# monthly_disk_operations: 0 # Number of disk operations (writes, reads, deletes) using a unit size of 256KiB.
# azurerm_linux_virtual_machine.curavm:
# monthly_hrs: 0 # Monthly number of hours the instance ran for.
# os_disk:
# monthly_disk_operations: 0 # Number of disk operations (writes, reads, deletes) using a unit size of 256KiB.
# azurerm_managed_disk.BIN:
# monthly_disk_operations: 0 # Number of disk operations (writes, reads, deletes) using a unit size of 256KiB.
--sync-usage-file --usage-file
busy-agent-35515
11/22/2022, 7:34 PM# Number of disk operations (writes, reads, deletes) using a unit size of 256KiB.
I think the easiest fix would be updating this comment to mention something like "Applies only for standard managed disks"best-action-5428
11/22/2022, 7:36 PMbusy-agent-35515
11/22/2022, 7:36 PMbest-action-5428
11/22/2022, 7:37 PMbusy-agent-35515
11/22/2022, 7:46 PMbest-action-5428
03/17/2023, 5:35 PMbusy-agent-35515
03/17/2023, 5:36 PM