Skip to Content
CatalogCatalog with Status Pages/Board

Catalog with Status Pages/Board

Catalog entities in Exemplar can be associated with incidents and maintenance events to provide accurate visibility across published status pages and status boards.

This integration helps teams communicate operational impact clearly while maintaining consistent service ownership and operational context.


How To: How to Preview Associated Incident with Services on the Published Status Board

How to Preview Associated Incident with Services on the Published Status BoardConsole walkthrough showing how incidents linked with catalog entities appear on published status boards.

Incident visibility through catalog associations

When incidents are linked to catalog entities, teams can publish operational updates directly to associated status boards.

This helps:

  • Display affected services clearly
  • Communicate operational impact to users
  • Maintain accurate incident visibility
  • Keep stakeholders informed during outages
  • Align incidents with service ownership

Operational teams can also manage which boards receive updates and how affected services appear during incident communication workflows.

Publishing incidents through linked catalog entities improves transparency and ensures service impact is reflected consistently across status boards.


How To: How to Preview Associated Maintenance with Services on the Published Status Board

How to Preview Associated Maintenance with Services on the Published Status BoardConsole walkthrough showing how maintenance events linked with catalog entities appear on published status boards.

Maintenance visibility and operational communication

Scheduled maintenance events can also be associated with catalog services and published to status boards.

This allows organizations to:

  • Inform users about planned work
  • Display affected systems proactively
  • Coordinate maintenance communication
  • Reflect service health changes during maintenance
  • Improve operational transparency

Maintenance publishing workflows help teams manage customer communication while keeping operational data aligned with catalog ownership and monitoring relationships.


Status boards and service context

Catalog associations create stronger relationships between:

  • Service ownership
  • Monitoring systems
  • Incidents and maintenance
  • Status communication
  • Operational visibility

By linking catalog entities with operational events, teams gain a centralized and more reliable operational experience across the platform.


Preview status boards and service visibility

To learn more about how incidents and maintenance workflows integrate with published status boards, visit:

This page covers how operational events appear across published status experiences and how catalog entities are reflected during incidents and maintenance workflows.


Best practices

  • Associate operational events with the correct catalog entities
  • Keep service ownership updated
  • Publish only relevant incidents and maintenance events
  • Review linked status boards regularly
  • Maintain accurate service naming conventions for customer visibility

Last updated on