Skip to content
Build

Service catalog

Map runtimes to services and owners your team recognizes.

Why keep a catalog?

A catalog helps a responder answer which system is affected and who owns it. It connects application nodes with service, project, and group names used by the team.

Start with operational boundaries

  1. Open Service Catalog and add the services people use when discussing the system.

  2. Group related services by product area or responsibility.

  3. Map instrumented nodes to the appropriate service and environment.

  4. Review ownership when teams or application boundaries change.

Keep it useful during an incident

Start with the services that matter for response rather than modeling every internal dependency. Use stable names and clear ownership so a new responder can find the right team without asking for a translation.