How to understand dimensions in Amberflo

amberflo metering cloud allows you to ask and answer the following question in realtime with guaranteed accuracy what was used, by whom, when, where, and how much? the flexible meter data structure in amberflo accomplishes this in the following way what = meter name and api whom = customer id when = timestamp how much = meter value where = dimensions as part of your meter definition you can add dimensions (custom key value pairs) to enrich meter records with additional custom metadata you might have one or more attributes related to the "where" aspect of the meter event for example where did this meter originate at (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 you can use dimensions to correlate a set of meter events together say you would like to like event e1 from meter a with event e2 from meter b you should create a shared credential which will be used to associate the two meters together (ie a session id) pass this session id as a dimension value for both event e1 and event e2 now when you search data by dimension, you can filter by session id to see correlated events some important things to note about dimension values dimension values are always stored as strings numerical values would not make sense to use as dimensions; if you are looking to aggregate these values then these would be their own meters boolean values can be handled by passing strings of "true" or "false" as needed if you need to use a url as a dimension value, the convention is to use "url" "https segment com" since you are altering the value of the url it would ahve to be transformed to its original state before being used downstream we can also encode the url like so https //abc com https //abc com/ > https%3a%2f%2fabc com this would also need to be decoded on the client side for viewing 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