Description

This article describes how to view the detailed Usage associated with your Cloud account using the Administrative UI. This report includes most of the billable elements and identifies how they contributed to the usage used for billing purposes. Software Units, Backup, and Monitoring usage are not included in this report as they are tracked in separate reports.

Prerequisites:

  1. Only the Primary Administrator or a User with the Reports role can generate Usage reports.
  2. Only one Detailed Usage report can be generated at a time per organization within a given Geographic Region. If a second user attempts to generate one simultaneously with another request, an error will result.
  3. The retention period for such reporting is one year. Data beyond one year old is not available.

Content / Solution:

  1. From the Home screen, click on the Compute menu, and select Download Reports from the drop-down menu:


  2. The Download Reports page will be displayed:


  3. Select "Detailed" from the drop-down menu:


  4. The system will ask you to define the Start and End dates for the report. The date range cannot be larger than 31 days. Click "Download" button when you've entered the dates:

    IMPORTANT NOTE: You will need to select an end date one day later than your actual desired end date for audit data. For example, if you want to generate a report showing Detailed Usage logs for the month of March 2016, your start date should be 3/1/16, but your end date should be 4/1/16.

    Note: A report cannot be generated for greater than a year earlier than the current date.
     

  5. The system will download a CSV formatted report that provides the details of every action performed by the organization during the time period selected. Opening up this file in Microsoft Excel or Google Docs is probably the easiest way of understanding the results.


  6. EXPLANATION OF COLUMNS IN DETAILED USAGE REPORT

    Important Information

    For ease of readability, the report has been broken down into 3 sections. Below you will find a screenshot accompanied by a description of the contents of that portion of the report.
    Note that when the report is downloaded from CloudControl, it will be one single report.


  • Name - Name of the Asset as of the time represented by the row.
  • UUID - Represents the Id of an asset. Even if the Name changes over time, the ID will remain constant.
    • Note: The Id of most types of assets are unique over time. However, IP blocks are not unique. A particular block of IP addresses (i..e 192.2.2.4 and 192.2.2.5) will always have the same Id. So if you add it to an account, later delete it, and end up receiving it again in the future, it will still have the same Id.
  • Type - Type of Asset (Server, Client Image, Sub-Administrator, etc).
  • Location - Data center location associated with the asset. Note that Sub-Administrators and Cloud File accounts are not associated with a specific location so this field is blank for that row.
  • Private IP Address - Private IP Address of the Cloud Server (MCP 1.0) or the Primary NIC IPv4 of the Cloud Server (MCP 2.0).
  • Status - Running or Stopped is displayed for Cloud Server rows to identify whether CPU/RAM charges are being incurred - these elements generate usage only when in the running state. Other Assets are always labeled Running.
  • Tag Keys (user: Tag Key Name) - Any column whose heading begins with "user<name of tag key>" is associated with a Tag Key that is currently set up to appear on the report (columns G & H in the above example). Tag Key columns assets will always appear in alphabetical order between the Status and StartTime columns. Currently, up to 5 Tag Keys can be reported on the Detailed Usage Report - for more details, see How to View and Manage Tag Keys for your Organization.
  • Start Time and End Time - Indicates the period of time for the row in question. Each time an asset changes state during a given day and that change would affect any of the usage elements on the detailed usage report, a new row is generated. See the "Explanation of Rows" section below for more details.
  • Duration (Hours) - Indicates the amount of time in hours that an asset was in a state during the reported time. 

  • CPU Type - Indicates the CPU Type associated with a Cloud Server (Standard, High Performance) during the reported time.
  • CPU Count - Indicates how many CPU are associated with a Cloud Server during the reported time.
  • RAM Type - Denotes the presence of "A-Series" Ram, which is only associated with Servers with CPU Latency Sensitivity set to High. 
  • RAM (GB) - Indicates how much RAM in GB is allotted to a Cloud Server during the reported time.
  • Standard Storage (GB), Provisioned IOPS Storage (GB), High-Performance Storage (GB), Economy Storage (GB) - Indicates how much Standard/Provisioned IOPS/High Performance/Economy Storage is allocated to a Cloud Server during the reported time.
  • Provisioned IOPS (Total IOPS) - Total IOPS assigned to all Disks that are assigned the Variable IOPS Disk Speed
  • Snapshot Status - Indicates the status of Snapshots on a Server. If a Server is in Snapshot Preview mode, this column will say "PREVIEW". Otherwise, this column will be blank. For more information on Snapshots, and Snapshot Usage, see
  • CPU Hours, Economy CPU Hours, High-Performance CPU Hours - Calculated based on the total CPU Count, the CPU speed and amount of time the server is running. For example, a Server with 1 High Performance CPU that is running for 10.5 hours will generate 10.5 High Performance CPU hours. A server with 16 Standard CPUs that is running for 10 hours will generate 160 CPU Hours.
    • 1-12 Standard CPU Hours13+ Standard CPU Hours, 1-12 Economy CPU Hours, 13+ Economy CPU Hours, 1-12 High Performance CPU Hours, and 13+ High Performance CPU Hours - Calculated in the same manner except that usage for the first 12 vCPU are assigned to the "1-12" element and all remaining CPU are assigned to the 13+ element. Using the same examples as above, a Server with 1 High Performance CPU that is running for 10.5 hours will generate 10.5 1-12 High Performance CPU hours and no 13+ High Performance CPU Hours. A server with 16 Standard CPUs that is running for 10 hours will generate 120 1-12 Standard CPU Hours (12 CPU x 10 Hours) and 40 13+ Standard CPU Hours (remaining 4 CPU x 10 Hours).
      For more information see Introduction to Usage Reporting
  • RAM Hours - Calculated based on the total GB of RAM and the amount of time the server is running. For example, a Server with 200 GB RAM that is running for 10 hours will generate 2000 RAM Hours.
    • 1-24 GB RAM Hours,  25-48 GB RAM Hours, 49-128 GB RAM Hours, 129-256 GB RAM Hours, and 257+ GB RAM Hours - Calculated in the same manner except that usage is assigned to each element based on the amount of RAM within that range. Using the same example above, a 200 GB RAM server running for 10 hours generates:
      • 1-24 GB RAM Hours is = First 24 GB RAM * 10 Hours = 240 
      • 25-48 GB RAM Hours is = Next 24 GB RAM * 10 Hours = 240
      • 49-128 GB RAM Hours = Next 80 GB RAM * 10 Hours = 800
      • 129-256 GB RAM Hours = 72 GB RAM (200 GB RAM - 128) * 10 Hours = 720
      • 257+ GB RAM Hours = 0
  • A-Series RAM Hours - Calculated based on the total GB of A-Series RAM and the amount of time the server is running. For example, a Server with 200 GB RAM that is running for 10 hours will generate 2000 A-Series RAM Hours.
    • 1-24 GB A-Series RAM Hours,  25-48 GB A-Series RAM Hours, 49-128 GB A-Series RAM Hours, 129-256 GB A-Series RAM Hours, and 257+ GB A-Series RAM Hours - Calculated in the same manner except that usage is assigned to each element based on the amount of A-Series RAM within that range. Using the same example above, a 200 GB A-Series RAM server running for 10 hours generates:
      • 1-24 GB A-Series RAM Hours is = First 24 GB RAM * 10 Hours = 240 
      • 25-48 GB A-Series RAM Hours is = Next 24 GB RAM * 10 Hours = 240
      • 49-128 GB A-Series RAM Hours = Next 80 GB RAM * 10 Hours = 800
      • 129-256 GB A-Series RAM Hours = 72 GB RAM (200 GB RAM - 128) * 10 Hours = 720
      • 257+ GB A-Series RAM Hours = 0
    • For more information see Introduction to Usage Reporting
  • Storage Hours, Provisioned IOPS Storage Hours, High Performance Storage HoursEconomy Storage Hours - Indicates the total amount of Storage Hours of a given storage type generated by the asset during the report time represented by the row. When a Cloud Server or Client Image exists (in the case of a Server, regardless of the running state), it generates usage for a type equal to the amount of storage of a given type multiplied by the Duration (Hours). Client Images only generate Storage Hours. For example, a Client Image of 50 GB of storage that exists for 24 hours will generate 1200 Storage Hours. A Cloud Server with 10 GB of High Performance Storage that exists for 10 hours will generate 100 High Performance Storage Hours. Rows associated with other assets will always show 0 for this column. See Introduction to Cloud Server Local Storage ("Disks") and Disk Speeds
  • Provisioned IOPS Hours - The total Provisioned IOPS multiplied by the duration of time the Cloud Server has been deployed with Variable IOPS Disks
    For example, a Cloud Server that has 5 Provisioned IOPS Disks, each with 1,000 IOPS assigned will generate 5,000 Provisioned IOPS Hours per hour, multiplied by duration (24 hours) would be 120,000 Provisioned IOPS Hours
  • Incoming Bandwidth (GB), Outgoing Bandwidth (GB) - Indicates the total amount of incoming and outgoing bandwidth in GB for a given Cloud Network or Cloud Network Domain during the reported time. Rows associated with other assets will always show 0 for this column.
  • Sub-Administrators - Generated by each Sub-Administrator added in addition to the Primary Administrator. When a Sub-Administrator exists, it generates usage equal to the Duration (Hours).
  • Networks - Generated by each Cloud Network deployed in MCP 1.0 locations. When a  Cloud Network exists, it generates usage equal to the Duration (Hours).
  • Essentials Network Domain Hours - Generated by each Essentials Network Domain deployed in MCP 2.0 locations. It generates usage equal to the Duration (Hours).
  • Advanced Network Domain Hours - Generated by Advanced Network Domains deployed in MCP 2.0 locations in the same manner as Essentials Network Domains.
  • Enterprise Network Domain Hours - Generated by Enterprise Network Domains deployed in MCP 2.0 locations in the same manner as Essentials and Advanced Network Domains.
  • VLAN Hours - Generated by each VLANs deployed in MCP 2.0 locations. Each VLAN generates usage equal to the Duration (Hours).
  • Additional Public IPs - Generated from additional Public IP blocks added to Cloud Networks (MCP 1.0) or Network Domains (MCP 2.0), Usage is generated by each IP address, so a block of 2 IP addresses will generate 2 Public IP hours per hour it is deployed.
  • DRS Storage (GB) - Generated by use of the DRS for Cloud feature. This column represents the amount of DRS Journal Storage being used by a Consistency Group during the reported time.
  • DRS Storage Hours - Generated by use of the DRS for Cloud feature. This column represents the amount of DRS Storage Hours billed for the reported time - equal to the DRS Storage (GB) times Duration (Hours).

EXPLANATION OF ROW BEHAVIOR IN DETAILED USAGE REPORT

  1. Cloud Servers - Each Cloud Server is displayed in multiple rows, with each row corresponding to a server state on a given day. A "server state" change occurs and a new row is generated if any of the following actions occur:
    1. Deployment or Deletion of Server (including the creation of Snapshot Preview servers)
    2. Change in CPU / RAM amount
    3. Change to Disk configuration, Disk Speed, Disk IOPS
    4. Change to CPU or RAM Speed
    5. Change to running state of the server (i.e. server started or stopped)
    6. Change in Snapshot Status 
      1. If a Server is in Snapshot Preview Mode, the associated column will say "PREVIEW". Otherwise, this column will be blank
    7. EXAMPLES OF CLOUD SERVER ROW BEHAVIOR IN THE SCREENSHOT ABOVE
      1. On 6/19/17 4:16 (row 2), "Server A" was deployed with 2 CPU (Standard Speed), 4 GB RAM, 10 GB Standard storage, and 15 GB Economy storage. You can see the CPU Hour elements, RAM elements, and storage elements usage generated based on this configuration and the duration shown in the Duration (Hours) column.
      2. On 6/19/17 11:17 (row 3), it was re-configured to a High Performance CPU. This resulted in the new row which shows it is now generating High Performance CPU Hour elements instead of Standard CPU hour elements
      3. On 6/19/17 11:17 (row 4), it had Essentials Snapshots service added which added a new row.
      4. Similarly, "Server B" was deployed in a running state on 6/19/17 3:42 (row 5), then stopped at 6/19/17 11:18 (row 6), and then reconfigured with less CPU and raw at 6/19/17 23:18 (row 7) with each change creating a new row. 
  2. Client Images - The system will display a row for each Client Image for whatever time it was deployed during the day. This is seen in rows 7 and 8.
  3. The system will display a row for each Sub-Administrator that was deployed during the day. This is seen in rows 11 and 12.
  4. The system will display a row for each Cloud Network (MCP 1.0) that was deployed during the day. This is seen in row 15. This row also includes the bandwidth associated with the Cloud Network.
  5. The system will display a row for each Cloud Network Domain (MCP 2.0) that was deployed during the day. This is seen in row 16 and 17. These rows include the bandwidth associated with the Cloud Network Domain.
    1. Note the report does not have a column that identifies whether a Network Domain is Essentials or Advanced. You can tell by whether the domain generates Essentials Network Domain Hours or Advanced Network Domain Hours.
    2. If a Network Domain is switched between Essentials/Advanced, an additional row is generated.
  6. The system will display a row for each VLAN (MCP 2.0) that was deployed during the day. This is seen in row 18.
  7. The system will display a row for each DRS Journal that was deployed during the day and identify the Consistency Group and location with which the DRS Journal is associated. Note that a Consistency Group uses a DRS Journal in both the Source and Target locations, so there will be two rows per Consistency Group per reported period. The DRS Journal Size and computed DRS Storage Hours are on the far right two columns of the report.  This is seen in rows 19 and 20.
  8. The system will display a row for each Additional IP Address block that was deployed during the day and identify the specific network, base IP, and the number of IP addresses in the block. This is seen in row 21.
  9. The system also adds a summary row for each day of the report. The report shows the calculated sub-total of all of the above rows (rounded up, per the pricing methodology where applicable) and total bandwidth usage for the day. This is seen in row 12.
  10. Impact of Tag Keys and Tagging:
    1. Each row is populated with the value associated with the Tag Key for that asset as of the reported time represented by a row. So when an asset is tagged, reporting will only include the tag as of the time of the tagging change. Historical rows prior to the change are not affected. If the Tag Key is applied to an asset without a corresponding value during the reporting period, the report will show "~unspecified~" for the value in that row
    2. Each time an asset's tags are changed, a new row is created for the asset regardless of whether the tag change is related to a Tag Key currently displayed on the report. Essentially, each "tag" of an asset is considered a state change.
  11. ADDITIONAL NOTES
    1. Each report is specific to the Geographic Region in which it is run. So running the report in the North America Geographic Region will only provide usage information for usage in North America data centers. If you want to view Europe usage, you need to run the report in the Europe Geographic Region.
    2. Reports are generated each day at midnight in the time zone of the Geographic Region. For details on these timezones, see Introduction to Geographic Regions.
  12. NOTE: This report does NOT include:
    1. Details of any OS Units generated by Cloud Servers. Those details are included in a separate report described in How to Create an OS Units Usage Report
    2. Details of any Software Units generated by Priced Software. Those details are included in a separate report described in How to Create a Software Usage Report.
    3. Details of Monitoring Usage. Those details are included in a separate report described in How to Create a Cloud Monitoring Report.
    4. Details of DRS Consistency Groups. These details are included in a separate report described in How to Generate a DRS Pairs Usage Report
    5. Details on Cloud Backup Usage. See Cloud Backup - How to Create a Backup Usage Report
  13. The system allocates approximately 3 minutes for generating a detailed usage report. Customers with large numbers of assets may exceed this "timeout value" in attempting to generate a report. The solution, in this case, is to "break up" the report request into separate date ranges. For example, if you are attempting to generate a report for March 1 to March 10 and receive an error, try generating a report for March 1 - March 5 and a separate request for March 6 - March 10. The files can then be easily combined to provide the required information.


It is possible that all of the elements listed in this article may not appear on a report that you generate. Elements will only be generated if they are available to your Organization.