Sign In

Catalog Integration

Status pages directly reference your catalog entities, eliminating duplicate component definitions and ensuring your status page always reflects reality.

How Integration Works

Traditional status pages force you to manually create components that duplicate your service definitions. This leads to drift, inconsistencies, and maintenance burden.

Upstat’s status pages reference your live catalog data:

  • Status updates automatically when monitors detect issues
  • Service relationships display correctly without configuration
  • New services appear as options immediately after catalog creation
  • Renamed entities update everywhere instantly
  • Deleted entities automatically remove themselves

Entity Selection

In the Status Page Editor

The Content tab connects your status page to catalog entities:

  1. Filter by Entity Type - Choose which types to display (Applications, Services, Infrastructure)
  2. Select Specific Entities - Pick individual entities or select entire categories
  3. Organize Display - Arrange entities in groups or hierarchies
  4. Preview Changes - See exactly how your selection appears to visitors

If you see “No entities found in catalog”, create catalog entities first—your status page can only display what exists in your catalog.

Perspective-Based Selection

Your perspective choice affects entity selection:

Traditional Perspective

  • Multi-select entities to display together
  • Organize into logical sections
  • Choose multiple entity types

Entity-Based Perspective

  • Select one primary entity as the focus
  • Automatically includes related entities
  • Dependencies discovered from catalog relationships

Automatic Status Updates

When monitors linked to catalog entities detect changes:

  1. Monitor status changes (Success → Fail)
  2. Entity health updates in the catalog
  3. Status page reflects the change instantly
  4. Subscribers notified if update is published

This happens automatically—no manual intervention required.

Relationship Display

Status pages can show entity relationships:

  • Service dependencies appear in context
  • Infrastructure backing services is visible
  • Parent/child relationships show hierarchy
  • Dependency graph available for entity-based perspective

Setting Up for Status Pages

1. Define Entity Types

Create categories matching your architecture:

  • Applications - Customer-facing services
  • Services - Backend APIs and microservices
  • Infrastructure - Databases, queues, cloud resources
  • External Dependencies - Third-party APIs

2. Create Entities

For each service:

  • Add descriptive name
  • Define relationships and dependencies
  • Link monitors for health tracking
  • Set operational metadata

3. Establish Relationships

Map how entities connect:

  • Service dependencies
  • Infrastructure requirements
  • Team ownership

Status Calculation

Traditional Perspective

  • Overall status reflects the worst state among all displayed entities
  • Each entity contributes equally to the summary
  • Simple aggregation of individual states

Entity-Based Perspective

  • Status reflects the primary entity’s health
  • Dependencies influence the overall assessment
  • More nuanced calculation based on relationships

Troubleshooting

“No entities found in catalog”

This appears when:

  • Catalog hasn’t been configured
  • User lacks permission to view entities
  • Entity filters exclude all available options

Solution: Create catalog entities first, then return to status page configuration.

Entities not appearing on public page

Check:

  • Entity is selected in status page configuration
  • Entity visibility settings allow public display
  • Status page is published (not draft)
  • Allow 30 seconds for cache refresh

Status not updating

Verify:

  • Monitors are attached to catalog entities
  • Monitor checks are running successfully
  • Event system is processing status changes