Use Case

Compute Cluster Management

  • Easily meter the runtime for any number of Compute Instances in real time
  • Aggregate, sort, and group meter data by instance type, number of cores, or any other custom identifier.
  • See real-time instance usage in dashboards and reflected on invoice balance .

Self-service tools to accurately track and charge for any compute-based use case

Each time an instance is activated, a meter is sent to Amberflo with a custom identifier for that instance (i.e. a cluster ID) indicating it started, with the time reported. When the instance is spun down, an additional meter event is sent to Amberflo (also tagged with the corresponding cluster ID) with a negative value which indicates that the instance became inactive. The difference between the two meters’ timestamps is recorded as the instance runtime.

Customize the data structure for any instance type or reporting need

By creating custom dimensions to capture attributes such as the instance type, number of cores, amount of memory, cloud provider and region and more, these dimensions can automatically be used in Amberflo Billing Cloud to build pricing plans that charge based on rates that are specific to these dimension combinations. In many cases customers will use these dimensions as differentiators in a Pricing Plan or compare usage between locations for reporting and forecasting purposes.

Visualize and query usage data in real time

As soon as the meter event is sent to Amberflo, it is persisted and aggregated in real time. The aggregated data appears in the Usage Explorer where users can filter and analyze data by meter, by customer, or by custom dimension. There is no latency or additional ETL required to track and visualize usage, it automatically appears in the Usage Explorer as it is ingested to Amberflo. Track resource consumption, data processing volumes and times, and any other metrics important to assessing the health and performance of the compute-based service.

Build flexible usage-based pricing plans

Build pricing plans with any number of product items (charge vectors), as well as custom artifacts such as a recurring fixed-rate charge (i.e. a platform fee), and automated rewards, promotions, and discounts. Charge by instance type, number of cores, amount of data processed, IT location, or any other custom dimension that makes sense. As an example consider EC2 where AWS charges customers based on the instance type, number of cores, and amount of memory that the accessed compute resource offers. In other cases, a vendor may want to charge for an event based on the cloud region or provider; since the backend costs for each location differ, it makes sense to charge a different rate to ensure the margin for the same service across locations is consistent.

Generate real-time metered invoices as usage occurs

Automatically generate updated metered invoices in real-time as usage occurs. When creating a Pricing Plan, Product Items are associated with the corresponding meter that provides the usage data. These meters are sent to Amberflo in real-time, and usage is aggregated, billed, and added to the running invoice for the current billing cycle as it is ingested. This means that users can see current invoices with the amount due at any point in the billing cycle, or set alerts to be notified when the usage or invoice amount reaches a certain threshold. Provide your customers complete transparency and real-time awareness to usage, consumption, and cost.

Alerting and Signaling

Create custom alerts and signals based on meter events or revenue thresholds. Signals can be defined based on a specific threshold value (i.e. when the customer consumes more compute than the starter plan allows, trigger an alert that directs the customer to upgrade to the paid plan or purchase additional credits to continue using the service), or a percent change over a time interval (i.e. a customer’s usage of a particular VM spiked by 575 percent in a day due to a change caused from an update pushed by the cloud provider; the signal notifies the customer of this change, and the customer can take action to rectify the misconfiguration and seek correction on the invoice). Signals can be configured to check if conditions are met daily, weekly, monthly or in real time to give users on both the customer and vendor side 24/7 visibility to usage, consumption, and cost.

Ready to Get Started