> ## Documentation Index
> Fetch the complete documentation index at: https://docs.obsy.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Services

> Manage your service catalog and track service health.

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:

| Tab           | Content                                                         |
| ------------- | --------------------------------------------------------------- |
| **Overview**  | Health status, recent alerts, linked incidents                  |
| **Telemetry** | Latest telemetry review results and coverage score              |
| **Changes**   | Recent deployments and Kubernetes events affecting this service |
| **Incidents** | All incidents where this service was listed as affected         |
| **Alerts**    | All alerts received for this service                            |

***

## 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:

```python theme={null}
# Python OTel
resource = Resource(attributes={"service.name": "payment-service"})
```

```yaml theme={null}
# Kubernetes pod env var
env:
  - name: OTEL_SERVICE_NAME
    value: payment-service
```

***

## Service environments

Each service is registered in one environment. If you run the same service in multiple environments (e.g. staging and production), register them as separate services:

* `payment-service` (production)
* `payment-service-staging` (staging)

Or use a shared name and track environments via alert tags.

***

## 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.