The catalog gives your team a common language to describe the systems, services, and entities that matter most. Whether it's a backend service, a product, or a customer—Upstat lets you define it and connect it to incidents.
Instead of scattered component lists or one-off labels, catalog entries provide structured, reusable context—across incidents, runbooks, status pages and more.
Define Key Entities
Capture your critical services, systems, and domains—across teams and environments.
Link Incidents to Context
Attach catalog entries to incidents so postmortems and analysis never happen in a vacuum.
Foundation for Status Pages
Use Catalog entries to define what your status pages represent—no need for a separate components.
Unified Across the Platform
Catalog entries appear anywhere context matters—from incidents to reporting to automation.
No two teams think about their infrastructure the same way. That's why Upstat's catalog lets you define your own types—like “Service”, “Product", “Platform”, or anything else—and assign custom fields to match.
Whether you need to track owners, deployment zones, compliance tags, or customer tiers, the catalog bends to your structure.
Custom Entity Types
Define exactly what kinds of things you want to track—services, customers, products, environments, and more.
Custom Fields per Type
Track metadata that matters: owners, deployment details, third-party dependencies, or anything else.
Flexible Without Complexity
Structure data for clarity without adding unnecessary overhead or rigidity.
Catalog entries in Upstat don't live in isolation—they're linked to the incidents, automations, runbooks, and anything else that references them. Open any catalog entity to see everything it's been associated with.
That means faster triage, better insights, and clearer accountability across your stack. When something matters, it's all connected—and all visible.
Linked Associations
See every place a catalog entry appears—incidents, runbooks, automations, and more.
Built-In Traceability
Understand how systems connect and overlap, directly from the Catalog.
Instant Visibility
Find out where an entity is used, what incidents it touched, and how it fits into your workflows.
The catalog isn't just for organizing—it's foundational. Whether you’re building an automation, assigning an incident, or auditing historical trends, catalog context makes it smarter, clearer, and more actionable.
That structure pays off everywhere: in your runbooks, your workflows, your postmortems, and your uptime reports.
Smarter Automations
Reference catalog fields and entities to trigger more specific, targeted actions.
Clearer Attribution
Understand which services are impacted most often and how teams are responding.
Future-Proof Reporting
Build structured reports tied to the systems that actually matter to your business.
Upstat's Catalog links services, teams, customers, and dependencies—so your responders know what's impacted, who owns it, and how to act faster.