Documentation

Service Catalog

Services are explicitly configured catalog entries. Mydle never invents services from raw telemetry. Link a project and optional telemetry name to compose monitors, deployments, browser, logs, traces, and incidents.

Ownership

Each service may define owner, team, Slack, email, and escalation contact. When missing, the UI shows Owner not configured — never guesses.

Dependencies

Upstream/downstream services, external APIs, databases, queues, and workers are stored as explicit edges (or evidence-backed edges with an evidence note). Empty sections stay hidden. We never infer edges without evidence.

Runbooks

Attach a runbook URL and/or body on the service Settings tab. Empty until configured.

Repository linking

Set repository name and URL on the service. Used for search and display only — not synced from git automatically in this sprint.

Health model

Per-service checks: Monitoring, Alerts, Incidents, Deployments, Browser, Logs, Tracing, Status. Pass / fail / unknown from linked evidence — no synthetic score.

Architecture

Compose-only on existing engines via projectId and optional telemetryName. Catalog tables: catalog_services, catalog_service_dependencies. Relationship Graph accepts ?serviceId=. See the ops report in the repository.

Product path: /app/services