Services and ownership

For engineering managers, engineers, administrators 4 min read

The service catalog: who owns what, what depends on what, and which services have no owner.

Services & ownership is your catalog of services, each with its owner, team, tier, dependencies and the services that depend on it. It's how ELOS knows who to route a question, an approval or a handover to.

Where services come from

Services and owners come from your connected tools, so connect source control first on Get started. The catalog is the view; your tools stay the source of truth.

Find a service

• Search the catalog and filter by tier: Tier 1, Tier 2 or Tier 3.
• The list is paged and sortable, so it stays fast for large estates.
• Open a service to see its owner, dependencies, what depends on it, and its recent activity.

Ownership

• A service with no current owner is an Orphan. ELOS flags orphans so nothing critical is left without an accountable owner.
• People with Edit service catalog can choose Assign owner or Edit service to update its metadata.
• When an owner leaves, their services are released and a successor is recommended. See Offboard and hand over.

Health, on-call and tier

• Health comes from a connected tool, never from a guess. With PagerDuty connected, a service with an open warning or critical incident is Degraded, and otherwise Healthy. A service no tool reports on shows Unknown.
• On call and Escalation come from PagerDuty while it's connected, and can't be edited by hand then: PagerDuty is where on-call is run.
• A service whose sources state no tier shows No tier. Set it in the service's catalog file, or with Edit service.