Why this matters: both features here solve a similar underlying problem — making Mavvrik's data model more flexible than what your cloud providers give you out of the box. Virtual Tags let you fix or backfill tagging without touching the underlying cloud resources; Perspectives let you define a reusable filtered view once instead of rebuilding it in every Budget, Alert, or dashboard that needs it.
This shows up differently depending on your role:
-
FinOps managers use Perspectives to define a standard view (e.g. "Production," "Team X") once and reference it everywhere, and Virtual Tags to backfill cost attribution for resources that were never tagged correctly.
-
Platform/admin teams set up both — creating the Virtual Tag rules and Perspective definitions that everyone else's Budgets, Alerts, and reports then build on.