The metering cycle distinguishes the metering data according to the local time zone where the platform service is provided.
The service to which the metered resource belongs.
The metered resource has one or more metering dimensions depending on its business characteristics, such as computing capability and storage capacity, and each resource detail corresponds to a different metering unit.
For detailed resource data, there may be multiple instances of the same service in an organization at the same time and such instances can generate different metering data. Therefore, the instance ID can be used to distinguish the source of the metering data. In general, an instance ID corresponds to a resource ID.
Refers to the amount of resources that a customer applies for through EnOS’s resource management services or allocated by the platform by default. There are two ways to allocate resource quota, namely: “pre-application” and “amount-based allocation”.
- Pre-application: Users need to apply for a certain amount of resources before they can use the services corresponding to these resources.
- EnOS Cloud will calculate according to the resource quota applied by users.
- If users need to upgrade to a higher resource quota, they need to apply for and purchase a higher resource quota for capacity expansion; otherwise the corresponding services would be restricted or stopped.
- Amount-based allocation: After the user activates a function or service, EnOS Cloud will meter the user’s actual consumption of resources without the need for the user to apply for and purchase the resource.
Quota Metering Statistics¶
From the user’s perspective, the resource quota metering statistics is the amount of resources for each EnOS service that was pre-applied for or used, which is calculated based on resource unit.