Workloads

workloads are amberflo’s way of representing internal systems or components that you want to attribute usage and cost to they provide a structured way to answer a simple question where is this usage happening, and what is it costing us? what is a workload? a workload represents a unit of infrastructure or functionality within your system examples include an image generation pipeline a customer support chatbot a recommendation engine a background processing job gpu clusters or compute resources any service or system that drives usage workloads are not tied to customers they are internal constructs used to organize and analyze usage and cost how workloads fit into the system workloads are used during metering when you send usage data, you can attach a workload identifier that usage is then attributed to that workload rated into cost using your cost models aggregated into spend views the same usage data can also be used for billing you are not forced to separate them you can use metering only for cost tracking use metering only for billing use the same meter for both cost and billing workloads sit on the cost side, but they work with the same underlying usage data workloads page overview navigate to the workloads page to view and manage your workloads what you’ll see each row in the table represents a workload and includes workload name current spend (month to date) created date expanding a workload click on a workload row to expand it you will see a list of previous months spend totals for each month drill into monthly spend click on a specific month to view detailed cost data this opens a breakdown similar to an invoice, where you can see all usage attributed to that workload how that usage was rated into cost the components contributing to total spend this is how you move from high level totals to detailed cost analysis creating a workload navigate go to the workloads page click create workload (top right) required fields a workload consists of two fields name a human readable label example image generation pipeline workload id a unique identifier used in meteringconstraints letters, numbers, hyphens, underscores only no spaces click save once complete how workloads are used in metering the workload id is critical when you send usage data to a meter, you include this id as part of the workload dimension example flow create a workload with id image pipeline send usage with workload = image pipeline amberflo attributes that usage to the workload cost is calculated and aggregated under that workload without this linkage, usage cannot be attributed to internal systems why workloads matter workloads allow you to understand which parts of your system drive cost compare spend across different services or pipelines identify high cost components track trends over time make informed optimization decisions this is typically used by engineering and infrastructure teams to analyze system efficiency monitor cost growth prioritize optimization efforts summary workloads are the foundation for internal cost attribution they represent parts of your infrastructure receive attributed usage through metering aggregate cost based on your rate models enable detailed analysis through spend views if you want to understand how your system consumes resources and where your costs come from, workloads are where that starts