Onboarding Walkthrough

Since Cloud Metering is a usage tracking system, the usage (as defined and collected by meters) must be attributed to something. Most often this will be a customer, but it can also be any other entity or object (e.g. department, project, group, environment, user, vehicle, etc.). You can create a customer record via the Console or API.
Note: CustomerID can also be supplied at the time of meter ingestion. Make a call to Customer Object API to create a customer ID and name.
- At the source where meter event originates.
- As an enrichment step between source and prior to Amberflo meter ingestion

📘 Further Reading
A meter is a resource being consumed or event to be tracked within the system you are looking to measure with the relevant dimensions (key-value pairs for custom metadata). They track the utilization of your system (what resource, how much, when, and by whom it is being consumed).

📘 Further Reading

Simply call the Amberflo meter ingestion endpoint or use the Ingest Meter View shown below.

📘 Further Reading

The next step is to create a pricing plan. You must provide a name for the plan and define the billing period as daily, weekly, monthly, or yearly.

Once the plan is created, you can add product items to the plan, apply fixed-rate add-ons and prepaid credits, and handle any custom currencies, rewards, or promotions.

📘 Further Reading

Amberflo can notify users of signals via email/web hooks/Slack. A signal can be defined on a specific customer, or on all customers based on a percentage change, threshold value, or absolute value.
Signal examples:
- Get an email for any customer that exceeds 1000 hours per week.
- Get a Slack message for any customer that uses 20% fewer resources week-over-week.


Below is an example of the message shown to users when the signal is thrown.
📘 Further Reading:

