Service Catalog

Note

The service catalog is available on all YipYap Cloud plans.

The service catalog provides a structured view of your infrastructure. It maps services to monitors, runbooks, and dependencies so your team has full context when responding to incidents.

Setup Guide

1. Navigate to Features > Service Catalog and click New Service.
2. Enter a name and description for the service (e.g. “Payment API”, “User Database”).
3. Assign one or more monitors that check this service’s health.
4. Attach runbooks with step-by-step recovery instructions for common failure scenarios.
5. Add context links to related resources (source repo, deployment pipeline, dashboards).
6. Under Dependencies, select any upstream services this service depends on.
7. Click Save.

Tip

Start by cataloging your most critical, customer-facing services first. You can always expand the catalog incrementally as your team builds the habit of documenting service ownership.

Creating a Service

1. Navigate to Features > Service Catalog.
2. Click New Service.
3. Enter a name and description (e.g. “Payment API”, “User Database”).
4. Assign one or more monitors to the service.
5. Click Save.

Runbooks

Attach runbooks to a service to give on-call responders step-by-step instructions for common incidents:

• Title: A short label (e.g. “Restart Payment Service”).
• Content: Markdown-formatted steps.
• URL: Optionally link to an external wiki or document.

When an alert fires for a monitor linked to a service, the runbook is surfaced in the alert notification and dashboard.

Context Links

Add links to related resources:

• Source code repository.
• Deployment pipeline.
• Monitoring dashboards.
• Architecture documentation.

These links appear on the service detail page and in alert context.

Dependency Graph

The dependency graph visualizes relationships between services. To define dependencies:

1. Open a service.
2. Under Dependencies, select other services that this service depends on.

The graph view shows upstream and downstream dependencies, helping you understand the blast radius of an incident.

Service Status

A service’s overall status is derived from its linked monitors:

Condition	Service Status
All monitors up	Operational
One or more monitors degraded	Degraded
One or more monitors down	Down