Onboarding Walkthrough

create customer 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 further reading for more information on creating customers in amberflo, create customers for the api reference, click here create meters 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 further reading for information on meter types and aggregation logic, click here for information on dimensions, meter dimensions for the api reference, click here ingest events simply call the amberflo meter ingestion endpoint or use the ingest meter view shown below 📘 further reading further reading for the api reference, click here for sdk options and sample code, click here https //docs amberflo io/docs/sdks create a pricing plan and associate it with a customer 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 further reading for the api reference, click here create alerts 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 further reading for the api reference, click here