Create Meters

to begin tracking usage in amberflo, you must first define meters that describe what you want to measure each meter acts as a structured contract between your systems and the amberflo platform, enabling consistent ingestion, attribution, and analysis of usage data start by navigating to the ai and cloud usage page by finding it on the left navigation list in the manage section or by using https //ui amberflo io/it spend/meters/list to create your first meter click on the + create meter button this guide walks you through the three main parts of a meter definition fields types of meters dimensions (additional metadata) 1\ meter fields each meter definition starts with three key fields label a human readable name for the meter, displayed in the dashboard meter api name a technical identifier used for event ingestion and backend processing description a short explanation of what the meter tracks, visible in the meter definition list these labels help users understand the purpose of each meter and allow systems to ingest data accurately 2\ meter types amberflo supports three distinct meter types each one is optimized for a different usage pattern count meters function increments the total value each time an event occurs tracking api calls counting transactions monitoring error occurrences easy to implementideal for volume based billing supports aggregation functions such as sum, avg, and max continuous meters function measures the duration between start and stop events or tracks the usage rate of a service/resource that is in continous use application uptime session duration cpu or memory usage precise measurement of time based or continuous usage suitable for resource billing and optimization seat based meters function tracks the number of active users, licenses, or instances over time software license compliance subscription user tracking capacity planning simplifies license tracking enables visibility into active consumption supports cost control for user based services choose the meter type that best fits the behavior of the resource or service you are metering 3\ meter dimensions dimensions are optional, but highly recommended, components of a meter definition they allow you to attach additional metadata to each meter event using key value pairs purpose of dimensions the following key questions are answered by the fields we've already discussed what was used (meter name) when it was used (timestamp) how much was used (meter value) dimensions help answer core finops questions in real time by whom it was used (business unit id) where or under what context it was used (dimension metadata) example dimension use cases data center project, department, or business unit cluster name or instance id event status or stage amberflo automatically recognizes and groups meter events by dimension values this enables powerful filtering, reporting, and pricing plan logic notes on usage dimensions are schemaless and do not need to be pre declared new dimensions are automatically added when they first appear in ingested events dimensions can be used to segment costs, define pricing plans, and apply promotions