Meter Dimensions

dimensions amberflo’s metering service enables you to answer key questions in real time with precision what was used, by whom, when, where, and how much? amberflo meter event data structure encapsulates this in the following way true 330,331 unhandled content type unhandled content type unhandled content type unhandled content type to support this, you can add dimensions to your meter definitions dimensions are custom key value pairs included with each meter event, allowing you to enrich the event data with contextual metadata what are dimensions? dimensions are the schemaless portion of a meter definition they provide a flexible way to customize the payload of a meter event without predefined constraints this allows you to capture and associate metadata such as where the usage originated (e g , cloud provider, region, zone) additional attribution beyond customer id (e g , cluster, project, department) event state or status any other business specific markers you are free to define any number of dimensions that reflect the context of your usage data important note if dimensions are not defined ahead of time, new ones are automatically created upon ingestion how dimensions are used grouping and filtering amberflo automatically groups and filters meter events by their dimension values for example, if you define a dimension called cloud provider with values such as aws, azure, or google, amberflo will automatically sort, group, and make those values filterable in the ui and apis pricing and d iscount s dimensions are not only useful for analytics but also play a key role in constructing pricing plans and discount rules you can use them to create pricing tiers, apply discounts, or define rate overrides based on specific dimension values usage explorer amberflo’s usage explorer provides real time visibility into aggregated meter events, grouped and pivoted by dimension this helps you analyze trends, drill into usage patterns, and segment your customers more effectively query api the query api allows you to extract aggregated usage data by dimension, enabling integration with external tools or downstream billing systems 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 for public cloud and department chargebacks { "meter name" "cloud bedrock input tokens", "meter value" 1725, "time" 1619445706909, "dimensions" { "business unit id" "us east 2", "region" "us east 2", "model" "anthropic claude 3 7 sonnet" } for customer billing { "customerid" "wayne enterprises, inc ", "meter name" "apicalls", "meter value" 575, "time" 1619445706909, "dimensions" { "region" "us east 2", "tenant type" "tech" }