Services is the catalog of every service the platform watches. For each service: owner team, tier (0/1/2), upstream dependencies, downstream consumers, SLOs and current burn, recent incident count, runbook links. Use it to answer "who owns this?" before paging the wrong team.
Each service has eight fields: name, owner team, tier, upstream dependencies, downstream consumers, SLOs and current burn, recent incident count, runbook links. The fields populate from a mix of auto-discovery (service graph) and explicit tags (Backstage / annotations). New services appear within minutes of their first traffic.
Six default filters: by team (mine, all), by tier (tier-0 only, all tiers), by health (unhealthy only, all), by environment (prod, staging), by region, by recent-incidents (services with > 3 incidents in 30d). Stack filters to narrow. Saved filters cover common operator queries.
Click any service for its drill-down: live SLI charts, incident history, ledger entries from agents acting on it, runbooks, dependencies map, owner contact. The drill-down is the place to answer any service-specific question without opening five other tools.
Services without an owner are a compliance and on-call risk. The page maintains an "unowned" filter that surfaces them. Unowned services show up in the weekly platform-admin report. Common causes: a team was renamed and the tag did not migrate, or a service was inherited from an acquisition. Either way, the page keeps the issue visible.
Subscribe to Nova AI Ops on YouTube for demos, tutorials, and feature deep-dives.
Services is the answer. Open the page, find the service, see the owner. Done.