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

# What is Obsy?

> Unified observability and incident response for Kubernetes teams.

Obsy is an observability platform built around **OpenTelemetry**. It manages your OTel collectors, keeps your telemetry high-quality and cost-efficient, and turns that data into fast incident response — alerts, AI root-cause analysis, postmortems, and a public status page, all in one place.

## Core capabilities

<CardGroup cols={2}>
  <Card title="OTel Collector Management" icon="satellite-dish">
    Deploy and manage OpenTelemetry gateway and node collectors across all your Kubernetes clusters from a single control plane.
  </Card>

  <Card title="Smart Sampling" icon="filter">
    Configure probabilistic or tail-based sampling with per-service overrides and endpoint/method drop rules to cut noise and cost.
  </Card>

  <Card title="Telemetry Review" icon="magnifying-glass-chart">
    AI-powered review of telemetry quality and coverage per service — identify missing spans, noisy logs, and coverage gaps.
  </Card>

  <Card title="Incident Management" icon="bell-alert">
    Create incidents, assign roles, spin up a dedicated Slack channel, and track a full timeline from alert to resolution.
  </Card>

  <Card title="AI Root Cause Analysis" icon="brain">
    Obsy analyzes alert signals, deployment changes, and telemetry to produce a structured root cause and recommended fix.
  </Card>

  <Card title="Postmortems" icon="book-open">
    Generate postmortems directly from resolved incidents. Keep a permanent record of what happened and how you fixed it.
  </Card>

  <Card title="Change Intelligence" icon="code-branch">
    Correlate alerts with Kubernetes events and CI/CD deployments so you always know what changed right before an outage.
  </Card>

  <Card title="Public Status Page" icon="globe">
    Publish a real-time status page for your customers with automatic incident linking, custom domains, and email subscriptions.
  </Card>
</CardGroup>

## How it fits together

```
Your services → OTel SDK
                    ↓
          OTel Collector (Gateway + Node)
            managed by Obsy
                    ↓
    ┌───────────────┴───────────────┐
 Datadog / Grafana              Obsy
 (metrics, traces, logs)     (telemetry quality,
                              sampling, cost)
                    ↓
             Alerts fire
                    ↓
     Obsy webhook → RCA → Incident
                    ↓
         Slack channel + status page
                    ↓
            Postmortem
```

## Next steps

<CardGroup cols={2}>
  <Card title="Quickstart" icon="rocket" href="/quickstart">
    Go from zero to a connected cluster in under 10 minutes.
  </Card>

  <Card title="Connect your platform" icon="plug" href="/getting-started/connect-platform">
    Link Datadog or Grafana to start receiving health data.
  </Card>
</CardGroup>