Templates
Service Catalog Template
A service catalog entry is the operational front door for a service. It should answer ownership, runtime, dependency, and support questions without a meeting.
Template
# Service: Name
## Summary
What the service does and why it exists.
## Ownership
- Owning team:
- Technical owner:
- Business owner:
- Slack or Teams channel:
- On-call rotation:
## Links
- Repository:
- Deployment pipeline:
- Infrastructure:
- Dashboard:
- Logs:
- Runbook:
- ADRs:
## Runtime
- Platform:
- Environments:
- Regions:
- Ingress:
- Dependencies:
## Data
- Datastores:
- Data classification:
- Retention:
- Backup and restore:
## Operations
- SLO:
- Alerts:
- Rollback path:
- Incident escalation:
## Security and compliance
- Authentication:
- Authorization:
- Secrets:
- Compliance scope:
- Required evidence:Catalog quality
Catalog entries should be generated or validated from systems of record where possible. Stale ownership data is worse than no catalog because it sends responders to the wrong place.