Overview
Track and connect everything your team relies on, from services to infrastructure.
The Catalog in Upstat helps you model the key entities in your system—starting with Services—and define how they relate to each other. These relationships add vital context for incident response, automation, reporting, and status pages.
What Is a Service?
A Service in Upstat is a core Catalog Entity. It can represent:
- An API or backend service
- A customer-facing application
- A third-party dependency
- A critical internal tool
- Any logical unit your team supports
Services can be added manually or via automation, and can be linked to monitors, incidents, automations, and more.
Defining Relationships
You can define relationships between Catalog Entities such as:
Depends on
Indicates that one service relies on anotherImpacts
Indicates that failure in this service affects the otherOwns
Assigns responsibility (e.g., a team or group owns a service)
These relationships help teams understand how components connect and what might be affected during incidents.
Using Relationships
Once defined, relationships power several parts of the platform:
Incidents
Show related services and dependencies when linked to a serviceStatus Pages
Let you select specific services to display publicly or internallyAutomations
Can be triggered based on events involving specific services or their dependenciesReports
Reports can be generated based on the entity relationships
Service Details
Clicking on a service opens its details panel, which shows:
- Metadata and custom fields
- Related incidents
- Linked monitors
- Defined relationships
This shows all information about that service in one place.
Summary
- Services represent key systems in your infrastructure
- Relationships define how services connect or depend on each other
- These associations drive clarity in incident response, automation, and reporting
- Services can be enriched with monitors, incidents, and metadata
Learn more