Monitoring costs in your subscription

The subscription overview allows you to monitor usage based costs. Have direct insights into what you pay and why.

You can easily monitor the usage and associated costs for a subscription. At the start of subscription periods, Service Plan fees are charged for the coming month as well as the accumulated costs for usage of the previous period. 


In this documentation, we will explore how to monitor usage for a subscription and explain the different types of usage costs.


Let’s get started🚀


Step 1: Log in to your wildcloud account and you will be navigated to the Applications page by default.



Step 2: Click on My Subscription option from the left menu bar of the interface.



This will navigate you to the subscription page where you can manage your subscription and can explore information related to your service plan and the timestamp of the account creation.



Step 3: Click on the Usage button, which is selected by default.



You can view and monitor the wildcloud Subscription usage and associated costs.


Parameters

Description

Period

Select the period from the dropdown to view the subscription cost for that period.

Total cost for period

Displays the total cost related to usage of subscription for the selected period. This excludes the Service plan fee.

Grouping

Select the grouping method from the dropdown menu. There are two ways to group the costs.


By application: Choosing this option shows the cost as per the number of applications. You can also apply a filter to choose either one of the applications or all.


By usage type: Choosing this option shows the cost as per the subscription usage type. You can also apply a filter to choose either one of the usage type or all. For more information on usage types, please see the list below.


Note: Every usage type is displayed in dollars while all metrics are measured in hours. Actual hourly prices per usage type can be found on the pricing page.



The different usage types that can appear in this overview are:


Tenant hours - Tenant hours is a usage type representing the sum of all hours in a certain period of time that your tenants existed. For example: Take a subscription with one application and one tenant, then for a given day the number of Tenant hours will be 24 hours. However, if a tenant gets added exactly at noon time, the number of Tenant hours for that day will be 36 and 48 for subsequent days. This usage is charged regardless of the scaling and compute settings of your application. This relates to the base cost of having a tenant for a certain number of hours.


Version hours -
Version hours is a usage type representing the sum of all hours in a certain period of time that versions existed, regardless of their status (Active or Shut down). For example, take a subscription with one application and one version, the number of version hours for a given day will be 24. However,  if an additional version is created on a day, exactly at noon,  then for that day the number of version hours will be 36 for that day and 48 for subsequent days. This usage is charged regardless of the status of the version and relates to the base cost of having a version for a certain number of hours


Version Container hours -
This usage is the sum of hours that versions have been in an active state, that is, the version editor was available and accessible. The Version hour usage is not affected by the status of the version, the number of Version Container hours is. To say that, on a given day in an application, a version was Active for 4 hours, then this usage will represent the cost for 4 hours of active version usage. To minimize this usage, turn off Versions that you are not actively working on. Turning off a version does not affect the Tenants that are running on said version, nor does it affect availability of snapshots for (automatized) tenant creation.

 

Metered [Small/General Purpose/Heavy Duty] - The metered usage will show the number of container hours that have been used to serve your tenants. Metered usage does not necessarily increase when increasing the number of tenants.


Cronjobs every [hour/half hour/quarter/5 minutes, minute] - This usage refers to the cronjob setting of your application. Increasing the cronjob frequency will increase the cost per tenant hour. For example, take an application with one tenant and Cronjobs running every minute, then for a given day, there will be 24 Cronjobs every minute tenant hours charged. If the number of tenants increases to 2 then there will be 48 hours charged.


Snapshot GigaByte Hours - Every snapshot requires storage. There is a 5 GB Month free tier to store snapshots per version. If the sum of the storage of snapshots is larger than the free tier, additional usage is charged per GigaByte hour.


Tenant Backup GigaByte Hours - Every tenant backup takes up storage. There is a 5 GB Month free tier to store backups per tenant. If the sum of the storage of backups is larger than the free tier, additional usage is charged per GigaByte hour.