Create and Manage a Catalog
The Catalog helps teams organize services, systems, APIs, infrastructure, and operational ownership in a centralized location.
It acts as the operational source of truth for incidents, maintenance, monitoring, and status visibility across the platform.
How To: Create and Manage a New Service Entity in the Catalog
Why the Catalog matters
Catalog entities provide structure and ownership across operational workflows.
They help teams:
- Track services and systems centrally
- Associate incidents and maintenance with affected components
- Link monitors and observability signals
- Maintain ownership and accountability
- Improve operational visibility across teams
The Catalog becomes especially important as organizations scale services and operational dependencies.
Create a new catalog entity
When creating a new entity, you can define:
- Entity Type — Such as service, system, or component
- Service Type — API, backend, frontend, database, and more
- Ownership — Assign responsible teams and maintainers
- Status — Active, development, deprecated, or other operational states
- Tags & Metadata — Improve organization and searchability
- Technology Stack — Languages and frameworks used by the service
These details help operational teams quickly understand service ownership, dependencies, and platform architecture.
Well-structured catalog entities improve incident response, maintenance coordination, and monitor visibility across the platform.
Manage and maintain catalog information
After creating an entity, teams can continue updating:
- Ownership and responsible teams
- External documentation links
- Additional metadata and operational context
- Technology stack information
- Service lifecycle status
Keeping catalog information updated ensures incidents, maintenance events, and status boards remain accurate and actionable.
Operational workflows supported by Catalog
Catalog entities integrate closely with other operational areas, including:
- Incident Management
- Maintenance Windows
- Synthetic Monitoring
- Status Pages & Boards
- Service Ownership and Escalation
This creates a unified operational workflow where teams can quickly identify affected systems and responsible owners during production events.
Best practices
- Use clear and standardized naming conventions
- Keep ownership assignments updated
- Add meaningful tags for filtering and discovery
- Link documentation and dashboards whenever possible
- Regularly review inactive or deprecated services