Skip to main content
The service catalog is Obsy’s central registry of your microservices. Services connect telemetry, incidents, alerts, and the status page together. Go to Services in the sidebar.

​
Adding a service

  1. Click Add service.
  2. Fill in:
    • Name — unique identifier used in alerts and telemetry (e.g. payment-service). Use the same name as your OTel service.name attribute.
    • Display name — human-readable name for the UI
    • Environment — production, staging, or development
    • Description — optional short description of what this service does
    • Team — assign to a team for ownership tracking
  3. Click Save.

​
Service detail

Click a service to open its detail page:

​
Linking services to OTel data

Obsy matches incoming alerts and telemetry to services by the service.name label/tag. Make sure the name in your OTel SDK instrumentation matches the service name in Obsy exactly (case-sensitive). Example:

​
Service environments

We recommend registering each environment as a separate service entry:
  • payment-service → production
  • payment-service-staging → staging
This gives you separate telemetry reviews, alert routing, and status page linking per environment — so a staging alert won’t trigger your production incident workflow. Alternatively, if you prefer a single service entry per service, use the Environment field and rely on alert tags (e.g. env:production) to distinguish environments. This works for alerts but means telemetry reviews cover all environments together.

​
Deleting a service

Open the service detail and click Delete service. This removes the service from the catalog. Existing alerts and incidents that reference this service are not deleted — they retain the service name as a string.