Usage Metering
Meter Dimensions
3min
dimensions amberflo metering service enables you to ask and answer the following questions in real time and with accuracy what was used by whom, when, where, and how much? amberflo meter event data structure encapsulates this in the following way what meter name and api name whom when how much where customerid timestamp meter value dimensions as part of your meter definition, you can add dimensions which are custom key value pairs added to meter event records dimensions are the schemaless portion of the meter definition it is a powerful metadata construct that gives you full flexibility in customizing the payload for a meter event you might have one or more attributes related to the "where" aspect of the meter event for example, where did this meter originate (e g cloud provider, region, zone, etc ) who, in addition to the customer id should i attribute this meter to (e g cluster name, project, department, etc ) state of the event other attributes/markers amberflo automatically groups and filters the meter events by dimensions for example, if you create a dimension name called cloud provider and send values ranging from (aws, azure, google, ), amberflo automatically sorts, groups and filters meter events by these dimension values these dimensions can also be used later to construct pricing plans and promotions dimensions serve an important function in a cloud metering service the concept allows you to enrich your meter records with custom fields and metadata important note if dimensions are not defined ahead of time, new ones are automatically created upon ingestion ingestion amberflo automatically pivots (aggregates and groups) meter events by each dimension using the usage reporting you can, in real time, view aggregated meter events sorted by dimension extraction amberflo query api enables you to extract aggregated meter events and values by dimension below are some common dimension types, but you are free to create any dimensions specific to your use case and domain additional resource or application ids department name cluster name or project name cloud region, zone, etc deployment environment customer type service version more { "tenant" "wayne enterprises, inc ", "tenant id" "54a43bba 915d 4512 a0bd 9d9debe2eb3a", "meter name" "apicalls", "meter value" 575, "time" 1619445706909, "dimensions" { "region" "us east 2", "tenant type" "tech" }