How to understand dimensions in Amberflo

amberflo metering cloud allows you to ask and answer the following question in real time with guaranteed accuracy what was used, by whom, when, where, and how much? the flexible meter data structure in amberflo enables this by mapping what = meter name and api whom = customer id when = timestamp how much = meter value where = dimensions what are dimensions? as part of your meter definition, you can include dimensions —custom key value pairs that enrich meter records with additional metadata examples of dimension use cases where indicate the origin (e g cloud provider, region, zone) who (additional) include internal identifiers like cluster name, project, or department state log the status or state of the event other markers include custom attributes specific to your use case amberflo automatically groups and filters meter events based on dimension values for example, if you define a dimension cloud provider with values like aws, azure, and google, the system can group usage by these providers correlating events using dimensions you can use dimensions to correlate related events from different meters for instance, if you want to link event e1 from meter a and event e2 from meter b , you can pass a shared key (e g session id) as a dimension for both events then, when querying, you can filter by this session id to view all correlated events important notes on dimensions stored as strings all dimension values are stored as strings don't use numerical values if you intend to perform aggregation—create a separate meter instead boolean values should be passed as "true" or "false" (as strings) using urls as dimension values conventionally use "url" "https segment com" or encode the url (e g , https //abc com becomes https%3a%2f%2fabc com) you’ll need to decode these values client side when displaying them the regex for dimensions is \[ ! '()&$ @=; +,?0 9a za z]{1,200} 📘 faqs and how tos docid\ bq14rede1rrwst00mbikx see related from metering and event ingestion how to measure a multi step process using a duration meter docid\ jejnqgjekdtlycfyxzsjj how to track seat based objects in amberflo docid\ k8g0vmh6adgukb3dmezay how to meter the number of active seats or users for a customer docid\ vyzt7z7cdkrhjyl avl68 how to verify the accuracy of meter data docid\ ne5rit1fjkfpatdbiej s how to track and bill for "high watermark" usage docid\ g l0lgdqyvfnccrsv2xbr how to handle erroneous or incorrect meters sent to amberflo docid\ awzcv2cw6swss2ffmcl58 how to find the meter id for retrieving and deleting a specific meter docid\ ty1vub6lz6u3fo nbfgb6 how to delete meters that are no longer in use docid\ x x7d16c6dwqrz zfdyvk how to handle high volume, high cardinality event streams docid\ edxld02jcxuqp2dkmd3 b