Skip to content

Cost & Telemetry — Cost as a First-Class Decision Signal

This guide defines how HybridOps.Studio collects, attributes, and gates cost signals so that DR and burst actions remain auditable, explainable, and budget-aware.

Goals

  • Treat cost as a first-class decision signal alongside availability and performance.
  • Attribute spend to run, environment, and component using consistent tags/labels.
  • Produce machine-readable evidence per run (JSON/CSV/MD) under output/artifacts/cost/.
  • Enforce budget guardrails before burst/DR actions and surface results in dashboards.

Standard Attribution

Use these keys consistently across Terraform, Packer, and CI/CD pipelines (mapped to Azure tags, GCP labels, and any internal metadata):

  • cost:env (for example dev | staging | prod)
  • cost:owner (for example hybridops-studio)
  • cost:component (for example ctrl01 | rke2 | netbox | edge)
  • cost:run_id (CI build number, pipeline ID, or UUID)
  • cost:purpose (for example dr-test | burst | baseline)

Terraform example

```hcl locals { cost_tags = { "cost:env" = var.env "cost:owner" = "hybridops-studio" "cost:component" = var.component "cost:run_id" = var.run_id "cost:purpose" = var.purpose } }

resource "azurerm_resource_group" "rg" { name = "${var.env}-rg" location = var.location tags = local.cost_tags }