Tags and ownership

OpsLyft routes findings, builds showback, and fills the Owner field on resources from your tags. The better your tag coverage, the less spend sits in unallocated.

The owner tagCopy Anchor Link

Your owner tag (for example team or owner) tells OpsLyft who owns each resource. It's used to:

• fill Owner and Team in Live inventory, Optimisation, and Anomalies;
• route tickets to the right Jira project;
• group cost by team in Cost Explorer and canvases.

Required tagsCopy Anchor Link

Required tags are the keys every resource should carry, such as team, env, and cost-center. Resources missing any of them get the Untagged signal, and the resource panel lists which are missing, such as 17 tags · 2 required missing.

CoverageCopy Anchor Link

Coverage is the share of spend that carries a tag. OpsLyft warns you in Needs attention when the owner tag covers too little spend to allocate or route by. Select Fix coverage to see the biggest untagged spend.

Check coverage anywhere by:

• opening Filter in Cost Explorer and reading the coverage bar next to a tag key;
• the Unallocated tile in Live inventory;
• the platform dataset tag_coverage (tag coverage by account).

See Allocate cost to teams for a step-by-step plan.